System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems

ABSTRACT

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an individual material bill of material and/or an order tracking view business object.

RELATED APPLICATION

This application claims the priority under 35 U.S.C. §119 of ProvisionalApplication Ser. No. 61/032,388 filed Feb. 28, 2008.

TECHNICAL FIELD

The subject matter described herein relates generally to the generationand use of consistent interfaces (or services) derived from a businessobject model. More particularly, the present disclosure relates to thegeneration and use of consistent interfaces or services that aresuitable for use across industries, across businesses, and acrossdifferent departments within a business.

BACKGROUND

Transactions are common among businesses and between businessdepartments within a particular business. During any given transaction,these business entities exchange information. For example, during asales transaction, numerous business entities may be involved, such as asales entity that sells merchandise to a customer, a financialinstitution that handles the financial transaction, and a warehouse thatsends the merchandise to the customer. The end-to-end businesstransaction may require a significant amount of information to beexchanged between the various business entities involved. For example,the customer may send a request for the merchandise as well as some formof payment authorization for the merchandise to the sales entity, andthe sales entity may send the financial institution a request for atransfer of funds from the customer's account to the sales entity'saccount.

Exchanging information between different business entities is not asimple task. This is particularly true because the information used bydifferent business entities is usually tightly tied to the businessentity itself. Each business entity may have its own program forhandling its part of the transaction. These programs differ from eachother because they typically are created for different purposes andbecause each business entity may use semantics that differ from theother business entities. For example, one program may relate toaccounting, another program may relate to manufacturing, and a thirdprogram may relate to inventory control. Similarly, one program mayidentify merchandise using the name of the product while another programmay identify the same merchandise using its model number. Further, onebusiness entity may use U.S. dollars to represent its currency whileanother business entity may use Japanese Yen. A simple difference informatting, e.g., the use of upper-case lettering rather than lower-caseor title-case, makes the exchange of information between businesses adifficult task. Unless the individual businesses agree upon particularsemantics, human interaction typically is required to facilitatetransactions between these businesses. Because these “heterogeneous”programs are used by different companies or by different business areaswithin a given company, a need exists for a consistent way to exchangeinformation and perform a business transaction between the differentbusiness entities.

Currently, many standards exist that offer a variety of interfaces usedto exchange business information. Most of these interfaces, however,apply to only one specific industry and are not consistent between thedifferent standards. Moreover, a number of these interfaces are notconsistent within an individual standard.

SUMMARY

In a first aspect, a computer readable medium includes program code forproviding a message-based interface for performing an individualmaterial bill of material service. The interface exposes at least oneservice as defined in a service registry. Upon execution, the programcode executes in an environment of computer systems providingmessage-based services. The service comprises program code forreceiving, from a service consumer, a first message for processinginformation for a list that comprises the elements defining anddescribing the components to assemble an individual material bill ofmaterial. Program code invokes an individual material bill of materialbusiness object. The business object is a logically centralized,semantically disjointed object for representing information for a listthat comprises the elements defining and describing the components toassemble an individual material bill of material. The business objectcomprises data logically organized as an individual material bill ofmaterial root node, and a variant subordinate node. The variant nodecontains a location subordinate node, and an item subordinate node. Theitem node contains a change state subordinate node. Program codeinitiates transmission of a message to a heterogeneous secondapplication, executing in the environment of computer systems providingmessage-based services, based on the data in the individual materialbill of material business object. The message comprises an individualmaterial bill of material message entity, a message header package, andan individual material bill of material package.

In a second aspect, a computer readable medium includes program code forproviding a message-based interface for performing an individualmaterial bill of material service. The software comprises computerreadable instructions embodied on tangible media. Upon execution, thesoftware executes in a landscape of computer systems providingmessage-based services. Program code initiates transmission of a messageto a heterogeneous second application, executing in the environment ofcomputer systems providing message-based services, based on data in anindividual material bill of material business object invoked by thesecond application. The business object is a logically centralized,semantically disjointed object for representing information for a listthat comprises the elements defining and describing the components toassemble an individual material bill of material. The business objectcomprises data logically organized as an individual material bill ofmaterial root node, and a variant subordinate node. The variant nodecontains a location subordinate node, and an item subordinate node. Theitem node contains a change state subordinate node. The messagecomprises an individual material bill of material message entity, amessage header package, and an individual material bill of materialpackage. Program code receives a second message from the secondapplication, the second message associated with the invoked individualmaterial bill of material business object and in response to the firstmessage.

In a third aspect, a distributed system operates in a landscape ofcomputer systems providing message-based services. The system processesbusiness objects involving an individual material bill of materialservice and comprises memory and a graphical user interface remote fromthe memory. The memory stores a business object repository storing aplurality of business objects. Each business object is a logicallycentralized, semantically disjointed object and at least one of thebusiness objects is for representing information for a list thatcomprises the elements defining and describing the components toassemble an individual material bill of material. The business objectcomprises data logically organized as an individual material bill ofmaterial root node, and a variant subordinate node. The variant nodecontains a location subordinate node, and an item subordinate node. Theitem node contains a change state subordinate node. The graphical userinterface remote from the memory presents data associated with aninvoked instance of the individual material bill of material businessobject, the interface comprising computer readable instructions embodiedon tangible media.

In a fourth aspect, a computer readable medium includes program code forproviding a message-based interface for performing an order trackingview service. The interface exposes at least one service as defined in aservice registry. Upon execution, the program code executes in anenvironment of computer systems providing message-based services. Theservice comprises program code for receiving, from a service consumer, afirst message for processing information for document information forthe follow-on business transactions for tracking and completion of aspecified order. Program code invokes an order tracking view businessobject. The business object is a logically centralized, semanticallydisjointed object for representing information for document informationfor the follow-on business transactions for tracking and completion of aspecified order. The business object comprises data logically organizedas an order tracking view root node, and an item subordinate node. Theitem node contains a product subordinate node, a quantity subordinatenode, a party subordinate node, a date subordinate node, a predecessorbusiness transaction document reference subordinate node, a logisticpackage subordinate node, and a schedule line subordinate node. Theschedule line node contains a quantity subordinate node, and a datesubordinate node. Program code initiates transmission of a message to aheterogeneous second application, executing in the environment ofcomputer systems providing message-based services, based on the data inthe order tracking view business object. The message comprises apurchase order tracking view enterprise resource planning by purchaseorder response message entity, a message header package, and a purchaseorder tracking view package, and a log package.

In a fifth aspect, a computer readable medium includes program code forproviding a message-based interface for performing an order trackingview service service. The software comprises computer readableinstructions embodied on tangible media. Upon execution, the softwareexecutes in a landscape of computer systems providing message-basedservices. The service comprises program code for initiating transmissionof a message to a heterogeneous second application, executing in theenvironment of computer systems providing message-based services, basedon data in a order tracking view business object invoked by the secondapplication. The business object is a logically centralized,semantically disjointed object for representing information for documentinformation for the follow-on business transactions for tracking andcompletion of a specified order. The business object comprises datalogically organized as an order tracking view root node, and an itemsubordinate node. The item node contains a product subordinate node, aquantity subordinate node, a party subordinate node, a date subordinatenode, a predecessor business transaction document reference subordinatenode, a logistic package subordinate node, and a schedule linesubordinate node. The schedule line node contains a quantity subordinatenode, and a date subordinate node. The message comprises a purchaseorder tracking view enterprise resource planning by purchase orderresponse message entity, a message header package, and a purchase ordertracking view package, and a log package. Program code receives a secondmessage from the second application, the second message associated withthe invoked order tracking view business object and in response to thefirst message.

In a sixth aspect, a distributed system operates in a landscape ofcomputer systems providing message-based services. The system processesbusiness objects involving an order tracking view service and comprisesmemory and a graphical user interface remote from the memory. The memorystores a business object repository storing a plurality of businessobjects. Each business object is a logically centralized, semanticallydisjointed object and at least one of the business objects is forrepresenting information for document information for the follow-onbusiness transactions for tracking and completion of a specified order.The business object comprises data logically organized as an ordertracking view root node, and an item subordinate node. The item nodecontains a product subordinate node, a quantity subordinate node, aparty subordinate node, a date subordinate node, a predecessor businesstransaction document reference subordinate node, a logistic packagesubordinate node, and a schedule line subordinate node. The scheduleline node contains a quantity subordinate node, and a date subordinatenode. The graphical user interface remote from the memory presents dataassociated with an invoked instance of the order tracking view businessobject, the interface comprising computer readable instructions embodiedon tangible media.

In some implementations, processing business objects includes creating,updating and/or retrieving information associated with the businessobjects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a flow diagram of the overall steps performed by methodsand systems consistent with the subject matter described herein.

FIG. 2 depicts a business document flow for an invoice request inaccordance with methods and systems consistent with the subject matterdescribed herein.

FIGS. 3A-B illustrate example environments implementing thetransmission, receipt, and processing of data between heterogeneousapplications in accordance with certain embodiments included in thepresent disclosure.

FIG. 4 illustrates an example application implementing certaintechniques and components in accordance with one embodiment of thesystem of FIG. 1.

FIG. 5A depicts an example development environment in accordance withone embodiment of FIG. 1.

FIG. 5B depicts a simplified process for mapping a model representationto a runtime representation using the example development environment ofFIG. 5A or some other development environment.

FIG. 6 depicts message categories in accordance with methods and systemsconsistent with the subject matter described herein.

FIG. 7 depicts an example of a package in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 8 depicts another example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 9 depicts a third example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 10 depicts a fourth example of a package in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 11 depicts the representation of a package in the XML schema inaccordance with methods and systems consistent with the subject matterdescribed herein.

FIG. 12 depicts a graphical representation of cardinalities between twoentities in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 13 depicts an example of a composition in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 14 depicts an example of a hierarchical relationship in accordancewith methods and systems consistent with the subject matter describedherein.

FIG. 15 depicts an example of an aggregating relationship in accordancewith methods and systems consistent with the subject matter describedherein.

FIG. 16 depicts an example of an association in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 17 depicts an example of a specialization in accordance withmethods and systems consistent with the subject matter described herein.

FIG. 18 depicts the categories of specializations in accordance withmethods and systems consistent with the subject matter described herein.

FIG. 19 depicts an example of a hierarchy in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 20 depicts a graphical representation of a hierarchy in accordancewith methods and systems consistent with the subject matter describedherein.

FIGS. 21A-B depict a flow diagram of the steps performed to create abusiness object model in accordance with methods and systems consistentwith the subject matter described herein.

FIGS. 22A-F depict a flow diagram of the steps performed to generate aninterface from the business object model in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 23 depicts an example illustrating the transmittal of a businessdocument in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 24 depicts an interface proxy in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 25 depicts an example illustrating the transmittal of a messageusing proxies in accordance with methods and systems consistent with thesubject matter described herein.

FIG. 26A depicts components of a message in accordance with methods andsystems consistent with the subject matter described herein.

FIG. 26B depicts IDs used in a message in accordance with methods andsystems consistent with the subject matter described herein.

FIGS. 27A-E depict a hierarchization process in accordance with methodsand systems consistent with the subject matter described herein.

FIG. 28 illustrates an example method for service enabling in accordancewith one embodiment of the present disclosure.

FIG. 29 is a graphical illustration of an example business object andassociated components as may be used in the enterprise serviceinfrastructure system of the present disclosure.

FIG. 30 illustrates an example method for managing a process agentframework in accordance with one embodiment of the present disclosure.

FIG. 31 illustrates an example method for status and action managementin accordance with one embodiment of the present disclosure.

FIG. 32 shows an exemplary IndividualMaterialBillOfMaterial MessageChoreography.

FIG. 33 shows an exemplary IndividualMaterialBillOfMaterialMessageMessage Data Type.

FIG. 34 shows an exemplaryIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_syncMessage Data Type.

FIG. 35 shows an exemplaryIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_syncMessage Data Type.

FIGS. 36-1 through 36-7 show an exemplaryIndividualMaterialBillOfMaterialMessage Element Structure.

FIGS. 37-1 through 37-2 show an exemplaryIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_syncElement Structure.

FIGS. 38-1 through 38-7 show an exemplaryIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_syncElement Structure.

FIG. 39 shows an exemplary OrderTrackingView Process Component.

FIG. 40 shows an exemplaryPurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync MessageData Type.

FIGS. 41-1 through 41-4 show an exemplaryPurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync MessageData Type.

FIGS. 42-1 through 42-16 show an exemplary OrderTrackingViewMessageElement Structure.

FIGS. 43-1 through 43-2 show an exemplaryPurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync ElementStructure.

FIGS. 44-1 through 44-12 show an exemplaryPurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync ElementStructure.

DETAILED DESCRIPTION

A. Overview

Methods and systems consistent with the subject matter described hereinfacilitate e-commerce by providing consistent interfaces that aresuitable for use across industries, across businesses, and acrossdifferent departments within a business during a business transaction.To generate consistent interfaces, methods and systems consistent withthe subject matter described herein utilize a business object model,which reflects the data that will be used during a given businesstransaction. An example of a business transaction is the exchange ofpurchase orders and order confirmations between a buyer and a seller.The business object model is generated in a hierarchical manner toensure that the same type of data is represented the same way throughoutthe business object model. This ensures the consistency of theinformation in the business object model. Consistency is also reflectedin the semantic meaning of the various structural elements. That is,each structural element has a consistent business meaning. For example,the location entity, regardless of in which package it is located,refers to a location.

From this business object model, various interfaces are derived toaccomplish the functionality of the business transaction. Interfacesprovide an entry point for components to access the functionality of anapplication. For example, the interface for a Purchase Order Requestprovides an entry point for components to access the functionality of aPurchase Order, in particular, to transmit and/or receive a PurchaseOrder Request. One skilled in the art will recognize that each of theseinterfaces may be provided, sold, distributed, utilized, or marketed asa separate product or as a major component of a separate product.Alternatively, a group of related interfaces may be provided, sold,distributed, utilized, or marketed as a product or as a major componentof a separate product. Because the interfaces are generated from thebusiness object model, the information in the interfaces is consistent,and the interfaces are consistent among the business entities. Suchconsistency facilitates heterogeneous business entities in cooperatingto accomplish the business transaction.

Generally, the business object is a representation of a type of auniquely identifiable business entity (an object instance) described bya structural model. In the architecture, processes may typically operateon business objects. Business objects represent a specific view on somewell-defined business content. In other words, business objectsrepresent content, which a typical business user would expect andunderstand with little explanation. Business objects are furthercategorized as business process objects and master data objects. Amaster data object is an object that encapsulates master data (i.e.,data that is valid for a period of time). A business process object,which is the kind of business object generally found in a processcomponent, is an object that encapsulates transactional data (i.e., datathat is valid for a point in time). The term business object will beused generically to refer to a business process object and a master dataobject, unless the context requires otherwise. Properly implemented,business objects are implemented free of redundancies.

The architectural elements also include the process component. Theprocess component is a software package that realizes a business processand generally exposes its functionality as services. The functionalitycontains business transactions. In general, the process componentcontains one or more semantically related business objects. Often, aparticular business object belongs to no more than one processcomponent. Interactions between process component pairs involving theirrespective business objects, process agents, operations, interfaces, andmessages are described as process component interactions, whichgenerally determine the interactions of a pair of process componentsacross a deployment unit boundary. Interactions between processcomponents within a deployment unit are typically not constrained by thearchitectural design and can be implemented in any convenient fashion.Process components may be modular and context-independent. In otherwords, process components may not be specific to any particularapplication and as such, may be reusable. In some implementations, theprocess component is the smallest (most granular) element of reuse inthe architecture. An external process component is generally used torepresent the external system in describing interactions with theexternal system; however, this should be understood to require no moreof the external system than that able to produce and receive messages asrequired by the process component that interacts with the externalsystem. For example, process components may include multiple operationsthat may provide interaction with the external system. Each operationgenerally belongs to one type of process component in the architecture.Operations can be synchronous or asynchronous, corresponding tosynchronous or asynchronous process agents, which will be describedbelow. The operation is often the smallest, separately-callablefunction, described by a set of data types used as input, output, andfault parameters serving as a signature.

The architectural elements may also include the service interface,referred to simply as the interface. The interface is a named group ofoperations. The interface often belongs to one process component andprocess component might contain multiple interfaces. In oneimplementation, the service interface contains only inbound or outboundoperations, but not a mixture of both. One interface can contain bothsynchronous and asynchronous operations. Normally, operations of thesame type (either inbound or outbound) which belong to the same messagechoreography will belong to the same interface. Thus, generally, alloutbound operations to the same other process component are in oneinterface.

The architectural elements also include the message. Operations transmitand receive messages. Any convenient messaging infrastructure can beused. A message is information conveyed from one process componentinstance to another, with the expectation that activity will ensue.Operation can use multiple message types for inbound, outbound, or errormessages. When two process components are in different deployment units,invocation of an operation of one process component by the other processcomponent is accomplished by the operation on the other processcomponent sending a message to the first process component.

The architectural elements may also include the process agent. Processagents do business processing that involves the sending or receiving ofmessages. Each operation normally has at least one associated processagent. Each process agent can be associated with one or more operations.Process agents can be either inbound or outbound and either synchronousor asynchronous. Asynchronous outbound process agents are called after abusiness object changes such as after a “create”, “update”, or “delete”of a business object instance. Synchronous outbound process agents aregenerally triggered directly by business object. An outbound processagent will generally perform some processing of the data of the businessobject instance whose change triggered the event. The outbound agenttriggers subsequent business process steps by sending messages usingwell-defined outbound services to another process component, whichgenerally will be in another deployment unit, or to an external system.The outbound process agent is linked to the one business object thattriggers the agent, but it is sent not to another business object butrather to another process component. Thus, the outbound process agentcan be implemented without knowledge of the exact business object designof the recipient process component. Alternatively, the process agent maybe inbound. For example, inbound process agents may be used for theinbound part of a message-based communication. Inbound process agentsare called after a message has been received. The inbound process agentstarts the execution of the business process step requested in a messageby creating or updating one or multiple business object instances.Inbound process agent is not generally the agent of business object butof its process component. Inbound process agent can act on multiplebusiness objects in a process component. Regardless of whether theprocess agent is inbound or outbound, an agent may be synchronous ifused when a process component requires a more or less immediate responsefrom another process component, and is waiting for that response tocontinue its work.

The architectural elements also include the deployment unit. Eachdeployment unit may include one or more process components that aregenerally deployed together on a single computer system platform.Conversely, separate deployment units can be deployed on separatephysical computing systems. The process components of one deploymentunit can interact with those of another deployment unit using messagespassed through one or more data communication networks or other suitablecommunication channels. Thus, a deployment unit deployed on a platformbelonging to one business can interact with a deployment unit softwareentity deployed on a separate platform belonging to a different andunrelated business, allowing for business-to-business communication.More than one instance of a given deployment unit can execute at thesame time, on the same computing system or on separate physicalcomputing systems. This arrangement allows the functionality offered bythe deployment unit to be scaled to meet demand by creating as manyinstances as needed.

Since interaction between deployment units is through process componentoperations, one deployment unit can be replaced by other anotherdeployment unit as long as the new deployment unit supports theoperations depended upon by other deployment units as appropriate. Thus,while deployment units can depend on the external interfaces of processcomponents in other deployment units, deployment units are not dependenton process component interaction within other deployment units.Similarly, process components that interact with other processcomponents or external systems only through messages, e.g., as sent andreceived by operations, can also be replaced as long as the replacementgenerally supports the operations of the original.

Services (or interfaces) may be provided in a flexible architecture tosupport varying criteria between services and systems. The flexiblearchitecture may generally be provided by a service delivery businessobject. The system may be able to schedule a service asynchronously asnecessary, or on a regular basis. Services may be planned according to aschedule manually or automatically. For example, a follow-up service maybe scheduled automatically upon completing an initial service. Inaddition, flexible execution periods may be possible (e.g. hourly,daily, every three months, etc.). Each customer may plan the services ondemand or reschedule service execution upon request.

FIG. 1 depicts a flow diagram 100 showing an example technique, perhapsimplemented by systems similar to those disclosed herein. Initially, togenerate the business object model, design engineers study the detailsof a business process, and model the business process using a “businessscenario” (step 102). The business scenario identifies the stepsperformed by the different business entities during a business process.Thus, the business scenario is a complete representation of a clearlydefined business process.

After creating the business scenario, the developers add details to eachstep of the business scenario (step 104). In particular, for each stepof the business scenario, the developers identify the complete processsteps performed by each business entity. A discrete portion of thebusiness scenario reflects a “business transaction,” and each businessentity is referred to as a “component” of the business transaction. Thedevelopers also identify the messages that are transmitted between thecomponents. A “process interaction model” represents the completeprocess steps between two components.

After creating the process interaction model, the developers create a“message choreography” (step 106), which depicts the messagestransmitted between the two components in the process interaction model.The developers then represent the transmission of the messages betweenthe components during a business process in a “business document flow”(step 108). Thus, the business document flow illustrates the flow ofinformation between the business entities during a business process.

FIG. 2 depicts an example business document flow 200 for the process ofpurchasing a product or service. The business entities involved with theillustrative purchase process include Accounting 202, Payment 204,Invoicing 206, Supply Chain Execution (“SCE”) 208, Supply Chain Planning(“SCP”) 210, Fulfillment Coordination (“FC”) 212, Supply RelationshipManagement (“SRM”) 214, Supplier 216, and Bank 218. The businessdocument flow 200 is divided into four different transactions:Preparation of Ordering (“Contract”) 220, Ordering 222, Goods Receiving(“Delivery”) 224, and Billing/Payment 226. In the business documentflow, arrows 228 represent the transmittal of documents. Each documentreflects a message transmitted between entities. One of ordinary skillin the art will appreciate that the messages transferred may beconsidered to be a communications protocol. The process flow follows thefocus of control, which is depicted as a solid vertical line (e.g., 229)when the step is required, and a dotted vertical line (e.g., 230) whenthe step is optional.

During the Contract transaction 220, the SRM 214 sends a Source ofSupply Notification 232 to the SCP 210. This step is optional, asillustrated by the optional control line 230 coupling this step to theremainder of the business document flow 200. During the Orderingtransaction 222, the SCP 210 sends a Purchase Requirement Request 234 tothe FC 212, which forwards a Purchase Requirement Request 236 to the SRM214. The SRM 214 then sends a Purchase Requirement Confirmation 238 tothe FC 212, and the FC 212 sends a Purchase Requirement Confirmation 240to the SCP 210. The SRM 214 also sends a Purchase Order Request 242 tothe Supplier 216, and sends Purchase Order Information 244 to the FC212. The FC 212 then sends a Purchase Order Planning Notification 246 tothe SCP 210. The Supplier 216, after receiving the Purchase OrderRequest 242, sends a Purchase Order Confirmation 248 to the SRM 214,which sends a Purchase Order Information confirmation message 254 to theFC 212, which sends a message 256 confirming the Purchase Order PlanningNotification to the SCP 210. The SRM 214 then sends an Invoice DueNotification 258 to Invoicing 206.

During the Delivery transaction 224, the FC 212 sends a DeliveryExecution Request 260 to the SCE 208. The Supplier 216 could optionally(illustrated at control line 250) send a Dispatched DeliveryNotification 252 to the SCE 208. The SCE 208 then sends a message 262 tothe FC 212 notifying the FC 212 that the request for the DeliveryInformation was created. The FC 212 then sends a message 264 notifyingthe SRM 214 that the request for the Delivery Information was created.The FC 212 also sends a message 266 notifying the SCP 210 that therequest for the Delivery Information was created. The SCE 208 sends amessage 268 to the FC 212 when the goods have been set aside fordelivery. The FC 212 sends a message 270 to the SRM 214 when the goodshave been set aside for delivery. The FC 212 also sends a message 272the SCP 210 when the goods have been set aside for delivery.

The SCE 208 sends a message 274 to the FC 212 when the goods have beendelivered. The FC 212 then sends a message 276 to the SRM 214 indicatingthat the goods have been delivered, and sends a message 278 to the SCP210 indicating that the goods have been delivered. The SCE 208 thensends an Inventory Change Accounting Notification 280 to Accounting 202,and an Inventory Change Notification 282 to the SCP 210. The FC 212sends an Invoice Due Notification 284 to Invoicing 206, and SCE 208sends a Received Delivery Notification 286 to the Supplier 216.

During the Billing/Payment transaction 226, the Supplier 216 sends anInvoice Request 287 to Invoicing 206. Invoicing 206 then sends a PaymentDue Notification 288 to Payment 204, a Tax Due Notification 289 toPayment 204, an Invoice Confirmation 290 to the Supplier 216, and anInvoice Accounting Notification 291 to Accounting 202. Payment 204 sendsa Payment Request 292 to the Bank 218, and a Payment RequestedAccounting Notification 293 to Accounting 202. Bank 218 sends a BankStatement Information 296 to Payment 204. Payment 204 then sends aPayment Done Information 294 to Invoicing 206 and a Payment DoneAccounting Notification 295 to Accounting 202.

Within a business document flow, business documents having the same orsimilar structures are marked. For example, in the business documentflow 200 depicted in FIG. 2, Purchase Requirement Requests 234, 236 andPurchase Requirement Confirmations 238, 240 have the same structures.Thus, each of these business documents is marked with an “O6.”Similarly, Purchase Order Request 242 and Purchase Order Confirmation248 have the same structures. Thus, both documents are marked with an“O1.” Each business document or message is based on a message type.

From the business document flow, the developers identify the businessdocuments having identical or similar structures, and use these businessdocuments to create the business object model (step 110). The businessobject model includes the objects contained within the businessdocuments. These objects are reflected as packages containing relatedinformation, and are arranged in a hierarchical structure within thebusiness object model, as discussed below.

Methods and systems consistent with the subject matter described hereinthen generate interfaces from the business object model (step 112). Theheterogeneous programs use instantiations of these interfaces (called“business document objects” below) to create messages (step 114), whichare sent to complete the business transaction (step 116). Businessentities use these messages to exchange information with other businessentities during an end-to-end business transaction. Since the businessobject model is shared by heterogeneous programs, the interfaces areconsistent among these programs. The heterogeneous programs use theseconsistent interfaces to communicate in a consistent manner, thusfacilitating the business transactions.

Standardized Business-to-Business (“B2B”) messages are compliant with atleast one of the e-business standards (i.e., they include thebusiness-relevant fields of the standard). The e-business standardsinclude, for example, RosettaNet for the high-tech industry, ChemicalIndustry Data Exchange (“CIDX”), Petroleum Industry Data Exchange(“PIDX”) for the oil industry, UCCnet for trade, PapiNet for the paperindustry, Odette for the automotive industry, HR-XML for humanresources, and XML Common Business Library (“xCBL”). Thus, B2B messagesenable simple integration of components in heterogeneous systemlandscapes. Application-to-Application (“A2A”) messages often exceed thestandards and thus may provide the benefit of the full functionality ofapplication components. Although various steps of FIG. 1 were describedas being performed manually, one skilled in the art will appreciate thatsuch steps could be computer-assisted or performed entirely by acomputer, including being performed by either hardware, software, or anyother combination thereof.

B. Implementation Details

As discussed above, methods and systems consistent with the subjectmatter described herein create consistent interfaces by generating theinterfaces from a business object model. Details regarding the creationof the business object model, the generation of an interface from thebusiness object model, and the use of an interface generated from thebusiness object model are provided below.

Turning to the illustrated embodiment in FIG. 3A, environment 300includes or is communicably coupled (such as via a one-, bi- ormulti-directional link or network) with server 302, one or more clients304, one or more or vendors 306, one or more customers 308, at leastsome of which communicate across network 312. But, of course, thisillustration is for example purposes only, and any distributed system orenvironment implementing one or more of the techniques described hereinmay be within the scope of this disclosure. Server 302 comprises anelectronic computing device operable to receive, transmit, process andstore data associated with environment 300. Generally, FIG. 3A providesmerely one example of computers that may be used with the disclosure.Each computer is generally intended to encompass any suitable processingdevice. For example, although FIG. 3A illustrates one server 302 thatmay be used with the disclosure, environment 300 can be implementedusing computers other than servers, as well as a server pool. Indeed,server 302 may be any computer or processing device such as, forexample, a blade server, general-purpose personal computer (PC),Macintosh, workstation, Unix-based computer, or any other suitabledevice. In other words, the present disclosure contemplates computersother than general purpose computers as well as computers withoutconventional operating systems. Server 302 may be adapted to execute anyoperating system including Linux, UNIX, Windows Server, or any othersuitable operating system. According to one embodiment, server 302 mayalso include or be communicably coupled with a web server and/or a mailserver.

As illustrated (but not required), the server 302 is communicablycoupled with a relatively remote repository 335 over a portion of thenetwork 312. The repository 335 is any electronic storage facility, dataprocessing center, or archive that may supplement or replace localmemory (such as 327). The repository 335 may be a central databasecommunicably coupled with the one or more servers 302 and the clients304 via a virtual private network (VPN), SSH (Secure Shell) tunnel, orother secure network connection. The repository 335 may be physically orlogically located at any appropriate location including in one of theexample enterprises or off-shore, so long as it remains operable tostore information associated with the environment 300 and communicatesuch data to the server 302 or at least a subset of plurality of theclients 304.

Illustrated server 302 includes local memory 327. Memory 327 may includeany memory or database module and may take the form of volatile ornon-volatile memory including, without limitation, magnetic media,optical media, random access memory (RAM), read-only memory (ROM),removable media, or any other suitable local or remote memory component.Illustrated memory 327 includes an exchange infrastructure (“XI”) 314,which is an infrastructure that supports the technical interaction ofbusiness processes across heterogeneous system environments. XI 314centralizes the communication between components within a businessentity and between different business entities. When appropriate, XI 314carries out the mapping between the messages. XI 314 integratesdifferent versions of systems implemented on different platforms (e.g.,Java and ABAP). XI 314 is based on an open architecture, and makes useof open standards, such as eXtensible Markup Language (XML)™ and Javaenvironments. XI 314 offers services that are useful in a heterogeneousand complex system landscape. In particular, XI 314 offers a runtimeinfrastructure for message exchange, configuration options for managingbusiness processes and message flow, and options for transformingmessage contents between sender and receiver systems.

XI 314 stores data types 316, a business object model 318, andinterfaces 320. The details regarding the business object model aredescribed below. Data types 316 are the building blocks for the businessobject model 318. The business object model 318 is used to deriveconsistent interfaces 320. XI 314 allows for the exchange of informationfrom a first company having one computer system to a second companyhaving a second computer system over network 312 by using thestandardized interfaces 320.

While not illustrated, memory 327 may also include business objects andany other appropriate data such as services, interfaces, VPNapplications or services, firewall policies, a security or access log,print or other reporting files, HTML files or templates, data classes orobject interfaces, child software applications or sub-systems, andothers. This stored data may be stored in one or more logical orphysical repositories. In some embodiments, the stored data (or pointersthereto) may be stored in one or more tables in a relational databasedescribed in terms of SQL statements or scripts. In the same or otherembodiments, the stored data may also be formatted, stored, or definedas various data structures in text files, XML documents, Virtual StorageAccess Method (VSAM) files, flat files, Btrieve files,comma-separated-value (CSV) files, internal variables, or one or morelibraries. For example, a particular data service record may merely be apointer to a particular piece of third party software stored remotely.In another example, a particular data service may be an internallystored software object usable by authenticated customers or internaldevelopment. In short, the stored data may comprise one table or file ora plurality of tables or files stored on one computer or across aplurality of computers in any appropriate format. Indeed, some or all ofthe stored data may be local or remote without departing from the scopeof this disclosure and store any type of appropriate data.

Server 302 also includes processor 325. Processor 325 executesinstructions and manipulates data to perform the operations of server302 such as, for example, a central processing unit (CPU), a blade, anapplication specific integrated circuit (ASIC), or a field-programmablegate array (FPGA). Although FIG. 3A illustrates a single processor 325in server 302, multiple processors 325 may be used according toparticular needs and reference to processor 325 is meant to includemultiple processors 325 where applicable. In the illustrated embodiment,processor 325 executes at least business application 330.

At a high level, business application 330 is any application, program,module, process, or other software that utilizes or facilitates theexchange of information via messages (or services) or the use ofbusiness objects. For example, application 330 may implement, utilize orotherwise leverage an enterprise service-oriented architecture(enterprise SOA), which may be considered a blueprint for an adaptable,flexible, and open IT architecture for developing services-based,enterprise-scale business solutions. This example enterprise service maybe a series of web services combined with business logic that can beaccessed and used repeatedly to support a particular business process.Aggregating web services into business-level enterprise services helpsprovide a more meaningful foundation for the task of automatingenterprise-scale business scenarios Put simply, enterprise services helpprovide a holistic combination of actions that are semantically linkedto complete the specific task, no matter how many cross-applications areinvolved. In certain cases, environment 300 may implement a compositeapplication 330, as described below in FIG. 4. Regardless of theparticular implementation, “software” may include software, firmware,wired or programmed hardware, or any combination thereof as appropriate.Indeed, application 330 may be written or described in any appropriatecomputer language including C, C++, Java, Visual Basic, assembler, Perl,any suitable version of 4GL, as well as others. For example, returningto the above mentioned composite application, the composite applicationportions may be implemented as Enterprise Java Beans (EJBs) or thedesign-time components may have the ability to generate run-timeimplementations into different platforms, such as J2EE (Java 2 Platform,Enterprise Edition), ABAP (Advanced Business Application Programming)objects, or Microsoft's .NET. It will be understood that whileapplication 330 is illustrated in FIG. 4 as including varioussub-modules, application 330 may include numerous other sub-modules ormay instead be a single multi-tasked module that implements the variousfeatures and functionality through various objects, methods, or otherprocesses. Further, while illustrated as internal to server 302, one ormore processes associated with application 330 may be stored,referenced, or executed remotely. For example, a portion of application330 may be a web service that is remotely called, while another portionof application 330 may be an interface object bundled for processing atremote client 304. Moreover, application 330 may be a child orsub-module of another software module or enterprise application (notillustrated) without departing from the scope of this disclosure.Indeed, application 330 may be a hosted solution that allows multiplerelated or third parties in different portions of the process to performthe respective processing.

More specifically, as illustrated in FIG. 4, application 330 may be acomposite application, or an application built on other applications,that includes an object access layer (OAL) and a service layer. In thisexample, application 330 may execute or provide a number of applicationservices, such as customer relationship management (CRM) systems, humanresources management (HRM) systems, financial management (FM) systems,project management (PM) systems, knowledge management (KM) systems, andelectronic file and mail systems. Such an object access layer isoperable to exchange data with a plurality of enterprise base systemsand to present the data to a composite application through a uniforminterface. The example service layer is operable to provide services tothe composite application. These layers may help the compositeapplication to orchestrate a business process in synchronization withother existing processes (e.g., native processes of enterprise basesystems) and leverage existing investments in the IT platform. Further,composite application 330 may run on a heterogeneous IT platform. Indoing so, composite application may be cross-functional in that it maydrive business processes across different applications, technologies,and organizations. Accordingly, composite application 330 may driveend-to-end business processes across heterogeneous systems orsub-systems. Application 330 may also include or be coupled with apersistence layer and one or more application system connectors. Suchapplication system connectors enable data exchange and integration withenterprise sub-systems and may include an Enterprise Connector (EC)interface, an Internet Communication Manager/Internet CommunicationFramework (ICM/ICF) interface, an Encapsulated PostScript (EPS)interface, and/or other interfaces that provide Remote Function Call(RFC) capability. It will be understood that while this exampledescribes a composite application 330, it may instead be a standalone or(relatively) simple software program. Regardless, application 330 mayalso perform processing automatically, which may indicate that theappropriate processing is substantially performed by at least onecomponent of environment 300. It should be understood that automaticallyfurther contemplates any suitable administrator or other userinteraction with application 330 or other components of environment 300without departing from the scope of this disclosure.

Returning to FIG. 3A, illustrated server 302 may also include interface317 for communicating with other computer systems, such as clients 304,over network 312 in a client-server or other distributed environment. Incertain embodiments, server 302 receives data from internal or externalsenders through interface 317 for storage in memory 327, for storage inDB 335, and/or processing by processor 325. Generally, interface 317comprises logic encoded in software and/or hardware in a suitablecombination and operable to communicate with network 312. Morespecifically, interface 317 may comprise software supporting one or morecommunications protocols associated with communications network 312 orhardware operable to communicate physical signals.

Network 312 facilitates wireless or wireline communication betweencomputer server 302 and any other local or remote computer, such asclients 304. Network 312 may be all or a portion of an enterprise orsecured network. In another example, network 312 may be a VPN merelybetween server 302 and client 304 across wireline or wireless link. Suchan example wireless link may be via 802.11a, 802.11b, 802.11g, 802.20,WiMax, and many others. While illustrated as a single or continuousnetwork, network 312 may be logically divided into various sub-nets orvirtual networks without departing from the scope of this disclosure, solong as at least portion of network 312 may facilitate communicationsbetween server 302 and at least one client 304. For example, server 302may be communicably coupled to one or more “local” repositories throughone sub-net while communicably coupled to a particular client 304 or“remote” repositories through another. In other words, network 312encompasses any internal or external network, networks, sub-network, orcombination thereof operable to facilitate communications betweenvarious computing components in environment 300. Network 312 maycommunicate, for example, Internet Protocol (IP) packets, Frame Relayframes, Asynchronous Transfer Mode (ATM) cells, voice, video, data, andother suitable information between network addresses. Network 312 mayinclude one or more local area networks (LANs), radio access networks(RANs), metropolitan area networks (MANs), wide area networks (WANs),all or a portion of the global computer network known as the Internet,and/or any other communication system or systems at one or morelocations. In certain embodiments, network 312 may be a secure networkassociated with the enterprise and certain local or remote vendors 306and customers 308. As used in this disclosure, customer 308 is anyperson, department, organization, small business, enterprise, or anyother entity that may use or request others to use environment 300. Asdescribed above, vendors 306 also may be local or remote to customer308. Indeed, a particular vendor 306 may provide some content tobusiness application 330, while receiving or purchasing other content(at the same or different times) as customer 308. As illustrated,customer 308 and vendor 06 each typically perform some processing (suchas uploading or purchasing content) using a computer, such as client304.

Client 304 is any computing device operable to connect or communicatewith server 302 or network 312 using any communication link. Forexample, client 304 is intended to encompass a personal computer, touchscreen terminal, workstation, network computer, kiosk, wireless dataport, smart phone, personal data assistant (PDA), one or more processorswithin these or other devices, or any other suitable processing deviceused by or for the benefit of business 308, vendor 306, or some otheruser or entity. At a high level, each client 304 includes or executes atleast GUI 336 and comprises an electronic computing device operable toreceive, transmit, process and store any appropriate data associatedwith environment 300. It will be understood that there may be any numberof clients 304 communicably coupled to server 302. Further, “client304,” “business,” “business analyst,” “end user,” and “user” may be usedinterchangeably as appropriate without departing from the scope of thisdisclosure. Moreover, for ease of illustration, each client 304 isdescribed in terms of being used by one user. But this disclosurecontemplates that many users may use one computer or that one user mayuse multiple computers. For example, client 304 may be a PDA operable towirelessly connect with external or unsecured network. In anotherexample, client 304 may comprise a laptop that includes an input device,such as a keypad, touch screen, mouse, or other device that can acceptinformation, and an output device that conveys information associatedwith the operation of server 302 or clients 304, including digital data,visual information, or GUI 336. Both the input device and output devicemay include fixed or removable storage media such as a magnetic computerdisk, CD-ROM, or other suitable media to both receive input from andprovide output to users of clients 304 through the display, namely theclient portion of GUI or application interface 336.

GUI 336 comprises a graphical user interface operable to allow the userof client 304 to interface with at least a portion of environment 300for any suitable purpose, such as viewing application or othertransaction data. Generally, GUI 336 provides the particular user withan efficient and user-friendly presentation of data provided by orcommunicated within environment 300. For example, GUI 336 may presentthe user with the components and information that is relevant to theirtask, increase reuse of such components, and facilitate a sizabledeveloper community around those components. GUI 336 may comprise aplurality of customizable frames or views having interactive fields,pull-down lists, and buttons operated by the user. For example, GUI 336is operable to display data involving business objects and interfaces ina user-friendly form based on the user context and the displayed data.In another example, GUI 336 is operable to display different levels andtypes of information involving business objects and interfaces based onthe identified or supplied user role. GUI 336 may also present aplurality of portals or dashboards. For example, GUI 336 may display aportal that allows users to view, create, and manage historical andreal-time reports including role-based reporting and such. Of course,such reports may be in any appropriate output format including PDF,HTML, and printable text. Real-time dashboards often provide table andgraph information on the current state of the data, which may besupplemented by business objects and interfaces. It should be understoodthat the term graphical user interface may be used in the singular or inthe plural to describe one or more graphical user interfaces and each ofthe displays of a particular graphical user interface. Indeed, referenceto GUI 336 may indicate a reference to the front-end or a component ofbusiness application 330, as well as the particular interface accessiblevia client 304, as appropriate, without departing from the scope of thisdisclosure. Therefore, GUI 336 contemplates any graphical userinterface, such as a generic web browser or touchscreen, that processesinformation in environment 300 and efficiently presents the results tothe user. Server 302 can accept data from client 304 via the web browser(e.g., Microsoft Internet Explorer or Netscape Navigator) and return theappropriate HTML or XML responses to the browser using network 312.

More generally in environment 300 as depicted in FIG. 3B, a FoundationLayer 375 can be deployed on multiple separate and distinct hardwareplatforms, e.g., System A 350 and System B 360, to support applicationsoftware deployed as two or more deployment units distributed on theplatforms, including deployment unit 352 deployed on System A anddeployment unit 362 deployed on System B. In this example, thefoundation layer can be used to support application software deployed inan application layer. In particular, the foundation layer can be used inconnection with application software implemented in accordance with asoftware architecture that provides a suite of enterprise serviceoperations having various application functionality. In someimplementations, the application software is implemented to be deployedon an application platform that includes a foundation layer thatcontains all fundamental entities that can used from multiple deploymentunits. These entities can be process components, business objects, andreuse service components. A reuse service component is a piece ofsoftware that is reused in different transactions. A reuse servicecomponent is used by its defined interfaces, which can be, e.g., localAPIs or service interfaces. As explained above, process components inseparate deployment units interact through service operations, asillustrated by messages passing between service operations 356 and 366,which are implemented in process components 354 and 364, respectively,which are included in deployment units 352 and 362, respectively. Asalso explained above, some form of direct communication is generally theform of interaction used between a business object, e.g., businessobject 358 and 368, of an application deployment unit and a businessobject, such as master data object 370, of the Foundation Layer 375.

Various components of the present disclosure may be modeled using amodel-driven environment. For example, the model-driven framework orenvironment may allow the developer to use simple drag-and-droptechniques to develop pattern-based or freestyle user interfaces anddefine the flow of data between them. The result could be an efficient,customized, visually rich online experience. In some cases, thismodel-driven development may accelerate the application developmentprocess and foster business-user self-service. It further enablesbusiness analysts or IT developers to compose visually rich applicationsthat use analytic services, enterprise services, remote function calls(RFCs), APIs, and stored procedures. In addition, it may allow them toreuse existing applications and create content using a modeling processand a visual user interface instead of manual coding.

FIG. 5A depicts an example modeling environment 516, namely a modelingenvironment, in accordance with one embodiment of the presentdisclosure. Thus, as illustrated in FIG. 5A, such a modeling environment516 may implement techniques for decoupling models created duringdesign-time from the runtime environment. In other words, modelrepresentations for GUIs created in a design time environment aredecoupled from the runtime environment in which the GUIs are executed.Often in these environments, a declarative and executable representationfor GUIs for applications is provided that is independent of anyparticular runtime platform, GUI framework, device, or programminglanguage.

According to some embodiments, a modeler (or other analyst) may use themodel-driven modeling environment 516 to create pattern-based orfreestyle user interfaces using simple drag-and-drop services. Becausethis development may be model-driven, the modeler can typically composean application using models of business objects without having to writemuch, if any, code. In some cases, this example modeling environment 516may provide a personalized, secure interface that helps unify enterpriseapplications, information, and processes into a coherent, role-basedportal experience. Further, the modeling environment 516 may allow thedeveloper to access and share information and applications in acollaborative environment. In this way, virtual collaboration roomsallow developers to work together efficiently, regardless of where theyare located, and may enable powerful and immediate communication thatcrosses organizational boundaries while enforcing security requirements.Indeed, the modeling environment 516 may provide a shared set ofservices for finding, organizing, and accessing unstructured contentstored in third-party repositories and content management systems acrossvarious networks 312. Classification tools may automate the organizationof information, while subject-matter experts and content managers canpublish information to distinct user audiences. Regardless of theparticular implementation or architecture, this modeling environment 516may allow the developer to easily model hosted business objects 140using this model-driven approach.

In certain embodiments, the modeling environment 516 may implement orutilize a generic, declarative, and executable GUI language (generallydescribed as XGL). This example XGL is generally independent of anyparticular GUI framework or runtime platform. Further, XGL is normallynot dependent on characteristics of a target device on which the graphicuser interface is to be displayed and may also be independent of anyprogramming language. XGL is used to generate a generic representation(occasionally referred to as the XGL representation or XGL-compliantrepresentation) for a design-time model representation. The XGLrepresentation is thus typically a device-independent representation ofa GUI. The XGL representation is declarative in that the representationdoes not depend on any particular GUI framework, runtime platform,device, or programming language. The XGL representation can beexecutable and therefore can unambiguously encapsulate executionsemantics for the GUI described by a model representation. In short,models of different types can be transformed to XGL representations.

The XGL representation may be used for generating representations ofvarious different GUIs and supports various GUI features including fullwindowing and componentization support, rich data visualizations andanimations, rich modes of data entry and user interactions, and flexibleconnectivity to any complex application data services. While a specificembodiment of XGL is discussed, various other types of XGLs may also beused in alternative embodiments. In other words, it will be understoodthat XGL is used for example description only and may be read to includeany abstract or modeling language that can be generic, declarative, andexecutable.

Turning to the illustrated embodiment in FIG. 5A, modeling tool 340 maybe used by a GUI designer or business analyst during the applicationdesign phase to create a model representation 502 for a GUI application.It will be understood that modeling environment 516 may include or becompatible with various different modeling tools 340 used to generatemodel representation 502. This model representation 502 may be amachine-readable representation of an application or a domain specificmodel. Model representation 502 generally encapsulates various designparameters related to the GUI such as GUI components, dependenciesbetween the GUI components, inputs and outputs, and the like. Putanother way, model representation 502 provides a form in which the oneor more models can be persisted and transported, and possibly handled byvarious tools such as code generators, runtime interpreters, analysisand validation tools, merge tools, and the like. In one embodiment,model representation 502 maybe a collection of XML documents with awell-formed syntax.

Illustrated modeling environment 516 also includes an abstractrepresentation generator (or XGL generator) 504 operable to generate anabstract representation (for example, XGL representation orXGL-compliant representation) 506 based upon model representation 502.Abstract representation generator 504 takes model representation 502 asinput and outputs abstract representation 506 for the modelrepresentation. Model representation 502 may include multiple instancesof various forms or types depending on the tool/language used for themodeling. In certain cases, these various different modelrepresentations may each be mapped to one or more abstractrepresentations 506. Different types of model representations may betransformed or mapped to XGL representations. For each type of modelrepresentation, mapping rules may be provided for mapping the modelrepresentation to the XGL representation 506. Different mapping rulesmay be provided for mapping a model representation to an XGLrepresentation.

This XGL representation 506 that is created from a model representationmay then be used for processing in the runtime environment. For example,the XGL representation 506 may be used to generate a machine-executableruntime GUI (or some other runtime representation) that may be executedby a target device. As part of the runtime processing, the XGLrepresentation 506 may be transformed into one or more runtimerepresentations, which may indicate source code in a particularprogramming language, machine-executable code for a specific runtimeenvironment, executable GUI, and so forth, which may be generated forspecific runtime environments and devices. Since the XGL representation506, rather than the design-time model representation, is used by theruntime environment, the design-time model representation is decoupledfrom the runtime environment. The XGL representation 506 can thus serveas the common ground or interface between design-time user interfacemodeling tools and a plurality of user interface runtime frameworks. Itprovides a self-contained, closed, and deterministic definition of allaspects of a graphical user interface in a device-independent andprogramming-language independent manner. Accordingly, abstractrepresentation 506 generated for a model representation 502 is generallydeclarative and executable in that it provides a representation of theGUI of model representation 502 that is not dependent on any device orruntime platform, is not dependent on any programming language, andunambiguously encapsulates execution semantics for the GUI. Theexecution semantics may include, for example, identification of variouscomponents of the GUI, interpretation of connections between the variousGUI components, information identifying the order of sequencing ofevents, rules governing dynamic behavior of the GUI, rules governinghandling of values by the GUI, and the like. The abstract representation506 is also not GUI runtime-platform specific. The abstractrepresentation 506 provides a self-contained, closed, and deterministicdefinition of all aspects of a graphical user interface that is deviceindependent and language independent.

Abstract representation 506 is such that the appearance and executionsemantics of a GUI generated from the XGL representation workconsistently on different target devices irrespective of the GUIcapabilities of the target device and the target device platform. Forexample, the same XGL representation may be mapped to appropriate GUIson devices of differing levels of GUI complexity (i.e., the sameabstract representation may be used to generate a GUI for devices thatsupport simple GUIs and for devices that can support complex GUIs), theGUI generated by the devices are consistent with each other in theirappearance and behavior.

Abstract representation generator 504 may be configured to generateabstract representation 506 for models of different types, which may becreated using different modeling tools 340. It will be understood thatmodeling environment 516 may include some, none, or other sub-modules orcomponents as those shown in this example illustration. In other words,modeling environment 516 encompasses the design-time environment (withor without the abstract generator or the various representations), amodeling toolkit (such as 340) linked with a developer's space, or anyother appropriate software operable to decouple models created duringdesign-time from the runtime environment. Abstract representation 506provides an interface between the design time environment and theruntime environment. As shown, this abstract representation 506 may thenbe used by runtime processing.

As part of runtime processing, modeling environment 516 may includevarious runtime tools 508 and may generate different types of runtimerepresentations based upon the abstract representation 506. Examples ofruntime representations include device or language-dependent (orspecific) source code, runtime platform-specific machine-readable code,GUIs for a particular target device, and the like. The runtime tools 508may include compilers, interpreters, source code generators, and othersuch tools that are configured to generate runtime platform-specific ortarget device-specific runtime representations of abstractrepresentation 506. The runtime tool 508 may generate the runtimerepresentation from abstract representation 506 using specific rulesthat map abstract representation 506 to a particular type of runtimerepresentation. These mapping rules may be dependent on the type ofruntime tool, characteristics of the target device to be used fordisplaying the GUI, runtime platform, and/or other factors. Accordingly,mapping rules may be provided for transforming the abstractrepresentation 506 to any number of target runtime representationsdirected to one or more target GUI runtime platforms. For example,XGL-compliant code generators may conform to semantics of XGL, asdescribed below. XGL-compliant code generators may ensure that theappearance and behavior of the generated user interfaces is preservedacross a plurality of target GUI frameworks, while accommodating thedifferences in the intrinsic characteristics of each and alsoaccommodating the different levels of capability of target devices.

For example, as depicted in example FIG. 5A, an XGL-to-Java compiler508A may take abstract representation 506 as input and generate Javacode 510 for execution by a target device comprising a Java runtime 512.Java runtime 512 may execute Java code 510 to generate or display a GUI514 on a Java-platform target device. As another example, anXGL-to-Flash compiler 508B may take abstract representation 506 as inputand generate Flash code 526 for execution by a target device comprisinga Flash runtime 518. Flash runtime 518 may execute Flash code 516 togenerate or display a GUI 520 on a target device comprising a Flashplatform. As another example, an XGL-to-DHTML (dynamic HTML) interpreter508C may take abstract representation 506 as input and generate DHTMLstatements (instructions) on the fly which are then interpreted by aDHTML runtime 522 to generate or display a GUI 524 on a target devicecomprising a DHTML platform.

It should be apparent that abstract representation 506 may be used togenerate GUIs for Extensible Application Markup Language (XAML) orvarious other runtime platforms and devices. The same abstractrepresentation 506 may be mapped to various runtime representations anddevice-specific and runtime platform-specific GUIs. In general, in theruntime environment, machine executable instructions specific to aruntime environment may be generated based upon the abstractrepresentation 506 and executed to generate a GUI in the runtimeenvironment. The same XGL representation may be used to generate machineexecutable instructions specific to different runtime environments andtarget devices.

According to certain embodiments, the process of mapping a modelrepresentation 502 to an abstract representation 506 and mapping anabstract representation 506 to some runtime representation may beautomated. For example, design tools may automatically generate anabstract representation for the model representation using XGL and thenuse the XGL abstract representation to generate GUIs that are customizedfor specific runtime environments and devices. As previously indicated,mapping rules may be provided for mapping model representations to anXGL representation. Mapping rules may also be provided for mapping anXGL representation to a runtime platform-specific representation.

Since the runtime environment uses abstract representation 506 ratherthan model representation 502 for runtime processing, the modelrepresentation 502 that is created during design-time is decoupled fromthe runtime environment. Abstract representation 506 thus provides aninterface between the modeling environment and the runtime environment.As a result, changes may be made to the design time environment,including changes to model representation 502 or changes that affectmodel representation 502, generally to not substantially affect orimpact the runtime environment or tools used by the runtime environment.Likewise, changes may be made to the runtime environment generally tonot substantially affect or impact the design time environment. Adesigner or other developer can thus concentrate on the design aspectsand make changes to the design without having to worry about the runtimedependencies such as the target device platform or programming languagedependencies.

FIG. 5B depicts an example process for mapping a model representation502 to a runtime representation using the example modeling environment516 of FIG. 5A or some other modeling environment. Model representation502 may comprise one or more model components and associated propertiesthat describe a data object, such as hosted business objects andinterfaces. As described above, at least one of these model componentsis based on or otherwise associated with these hosted business objectsand interfaces. The abstract representation 506 is generated based uponmodel representation 502. Abstract representation 506 may be generatedby the abstract representation generator 504. Abstract representation506 comprises one or more abstract GUI components and propertiesassociated with the abstract GUI components. As part of generation ofabstract representation 506, the model GUI components and theirassociated properties from the model representation are mapped toabstract GUI components and properties associated with the abstract GUIcomponents. Various mapping rules may be provided to facilitate themapping. The abstract representation encapsulates both appearance andbehavior of a GUI. Therefore, by mapping model components to abstractcomponents, the abstract representation not only specifies the visualappearance of the GUI but also the behavior of the GUI, such as inresponse to events whether clicking/dragging or scrolling, interactionsbetween GUI components and such.

One or more runtime representations 550 a, including GUIs for specificruntime environment platforms, may be generated from abstractrepresentation 506. A device-dependent runtime representation may begenerated for a particular type of target device platform to be used forexecuting and displaying the GUI encapsulated by the abstractrepresentation. The GUIs generated from abstract representation 506 maycomprise various types of GUI elements such as buttons, windows,scrollbars, input boxes, etc. Rules may be provided for mapping anabstract representation to a particular runtime representation. Variousmapping rules may be provided for different runtime environmentplatforms.

Methods and systems consistent with the subject matter described hereinprovide and use interfaces 320 derived from the business object model318 suitable for use with more than one business area, for exampledifferent departments within a company such as finance, or marketing.Also, they are suitable across industries and across businesses.Interfaces 320 are used during an end-to-end business transaction totransfer business process information in an application-independentmanner. For example the interfaces can be used for fulfilling a salesorder.

1. Message Overview

To perform an end-to-end business transaction, consistent interfaces areused to create business documents that are sent within messages betweenheterogeneous programs or modules.

(a) Message Categories

As depicted in FIG. 6, the communication between a sender 602 and arecipient 604 can be broken down into basic categories that describe thetype of the information exchanged and simultaneously suggest theanticipated reaction of the recipient 604. A message category is ageneral business classification for the messages. Communication issender-driven. In other words, the meaning of the message categories isestablished or formulated from the perspective of the sender 602. Themessage categories include information 606, notification 608, query 610,response 612, request 614, and confirmation 616.

(i) Information

Information 606 is a message sent from a sender 602 to a recipient 604concerning a condition or a statement of affairs. No reply toinformation is expected. Information 606 is sent to make businesspartners or business applications aware of a situation. Information 606is not compiled to be application-specific. Examples of “information”are an announcement, advertising, a report, planning information, and amessage to the business warehouse.

(ii) Notification

A notification 608 is a notice or message that is geared to a service. Asender 602 sends the notification 608 to a recipient 604. No reply isexpected for a notification. For example, a billing notification relatesto the preparation of an invoice while a dispatched deliverynotification relates to preparation for receipt of goods.

(iii) Query

A query 610 is a question from a sender 602 to a recipient 604 to whicha response 612 is expected. A query 610 implies no assurance orobligation on the part of the sender 602. Examples of a query 610 arewhether space is available on a specific flight or whether a specificproduct is available. These queries do not express the desire forreserving the flight or purchasing the product.

(iv) Response

A response 612 is a reply to a query 610. The recipient 604 sends theresponse 612 to the sender 602. A response 612 generally implies noassurance or obligation on the part of the recipient 604. The sender 602is not expected to reply. Instead, the process is concluded with theresponse 612. Depending on the business scenario, a response 612 alsomay include a commitment, i.e., an assurance or obligation on the partof the recipient 604. Examples of responses 612 are a response statingthat space is available on a specific flight or that a specific productis available. With these responses, no reservation was made.

(v) Request

A request 614 is a binding requisition or requirement from a sender 602to a recipient 604. Depending on the business scenario, the recipient604 can respond to a request 614 with a confirmation 616. The request614 is binding on the sender 602. In making the request 614, the sender602 assumes, for example, an obligation to accept the services renderedin the request 614 under the reported conditions. Examples of a request614 are a parking ticket, a purchase order, an order for delivery and ajob application.

(vi) Confirmation

A confirmation 616 is a binding reply that is generally made to arequest 614. The recipient 604 sends the confirmation 616 to the sender602. The information indicated in a confirmation 616, such as deadlines,products, quantities and prices, can deviate from the information of thepreceding request 614. A request 614 and confirmation 616 may be used innegotiating processes. A negotiating process can consist of a series ofseveral request 614 and confirmation 616 messages. The confirmation 616is binding on the recipient 604. For example, 100 units of X may beordered in a purchase order request; however, only the delivery of 80units is confirmed in the associated purchase order confirmation.

(b) Message Choreography

A message choreography is a template that specifies the sequence ofmessages between business entities during a given transaction. Thesequence with the messages contained in it describes in general themessage “lifecycle” as it proceeds between the business entities. Ifmessages from a choreography are used in a business transaction, theyappear in the transaction in the sequence determined by thechoreography. This illustrates the template character of a choreography,i.e., during an actual transaction, it is not necessary for all messagesof the choreography to appear. Those messages that are contained in thetransaction, however, follow the sequence within the choreography. Abusiness transaction is thus a derivation of a message choreography. Thechoreography makes it possible to determine the structure of theindividual message types more precisely and distinguish them from oneanother.

2. Components of the Business Object Model

The overall structure of the business object model ensures theconsistency of the interfaces that are derived from the business objectmodel. The derivation ensures that the same business-related subjectmatter or concept is represented and structured in the same way in allinterfaces.

The business object model defines the business-related concepts at acentral location for a number of business transactions. In other words,it reflects the decisions made about modeling the business entities ofthe real world acting in business transactions across industries andbusiness areas. The business object model is defined by the businessobjects and their relationship to each other (the overall netstructure).

Each business object is generally a capsule with an internalhierarchical structure, behavior offered by its operations, andintegrity constraints. Business objects are semantically disjoint, i.e.,the same business information is represented once. In the businessobject model, the business objects are arranged in an orderingframework. From left to right, they are arranged according to theirexistence dependency to each other. For example, the customizingelements may be arranged on the left side of the business object model,the strategic elements may be arranged in the center of the businessobject model, and the operative elements may be arranged on the rightside of the business object model. Similarly, the business objects arearranged from the top to the bottom based on defined order of thebusiness areas, e.g., finance could be arranged at the top of thebusiness object model with CRM below finance and SRM below CRM.

To ensure the consistency of interfaces, the business object model maybe built using standardized data types as well as packages to grouprelated elements together, and package templates and entity templates tospecify the arrangement of packages and entities within the structure.

(a) Data Types

Data types are used to type object entities and interfaces with astructure. This typing can include business semantic. Such data typesmay include those generally described at pages 96 through 1642 (whichare incorporated by reference herein) of U.S. patent application Ser.No. 11/803,178, filed on May 11, 2007 and entitled “Consistent Set OfInterfaces Derived From A Business Object Model”. For example, the datatype BusinessTransactionDocumentID is a unique identifier for a documentin a business transaction. Also, as an example, Data typeBusinessTransactionDocumentParty contains the information that isexchanged in business documents about a party involved in a businesstransaction, and includes the party's identity, the party's address, theparty's contact person and the contact person's address.BusinessTransactionDocumentParty also includes the role of the party,e.g., a buyer, seller, product recipient, or vendor.

The data types are based on Core Component Types (“CCTs”), whichthemselves are based on the World Wide Web Consortium (“W3C”) datatypes. “Global” data types represent a business situation that isdescribed by a fixed structure. Global data types include bothcontext-neutral generic data types (“GDTs”) and context-based contextdata types (“CDTs”). GDTs contain business semantics, but areapplication-neutral, i.e., without context. CDTs, on the other hand, arebased on GDTs and form either a use-specific view of the GDTs, or acontext-specific assembly of GDTs or CDTs. A message is typicallyconstructed with reference to a use and is thus a use-specific assemblyof GDTs and CDTs. The data types can be aggregated to complex datatypes.

To achieve a harmonization across business objects and interfaces, thesame subject matter is typed with the same data type. For example, thedata type “GeoCoordinates” is built using the data type “Measure” sothat the measures in a GeoCoordinate (i.e., the latitude measure and thelongitude measure) are represented the same as other “Measures” thatappear in the business object model.

(b) Entities

Entities are discrete business elements that are used during a businesstransaction. Entities are not to be confused with business entities orthe components that interact to perform a transaction. Rather,“entities” are one of the layers of the business object model and theinterfaces. For example, a Catalogue entity is used in a CataloguePublication Request and a Purchase Order is used in a Purchase OrderRequest. These entities are created using the data types defined aboveto ensure the consistent representation of data throughout the entities.

(c) Packages

Packages group the entities in the business object model and theresulting interfaces into groups of semantically associated information.Packages also may include “sub”-packages, i.e., the packages may benested.

Packages may group elements together based on different factors, such aselements that occur together as a rule with regard to a business-relatedaspect. For example, as depicted in FIG. 7, in a Purchase Order,different information regarding the purchase order, such as the type ofpayment 702, and payment card 704, are grouped together via thePaymentInformation package 700.

Packages also may combine different components that result in a newobject. For example, as depicted in FIG. 8, the components wheels 804,motor 806, and doors 808 are combined to form a composition “Car” 802.The “Car” package 800 includes the wheels, motor and doors as well asthe composition “Car.”

Another grouping within a package may be subtypes within a type. Inthese packages, the components are specialized forms of a genericpackage. For example, as depicted in FIG. 9, the components Car 904,Boat 906, and Truck 908 can be generalized by the generic term Vehicle902 in Vehicle package 900. Vehicle in this case is the generic package910, while Car 912, Boat 914, and Truck 916 are the specializations 918of the generalized vehicle 910.

Packages also may be used to represent hierarchy levels. For example, asdepicted in FIG. 10, the Item Package 1000 includes Item 1002 withsubitem xxx 1004, subitem yyy 1006, and subitem zzz 1008.

Packages can be represented in the XML schema as a comment. Oneadvantage of this grouping is that the document structure is easier toread and is more understandable. The names of these packages areassigned by including the object name in brackets with the suffix“Package.” For example, as depicted in FIG. 11, Party package 1100 isenclosed by <PartyPackage> 1102 and </PartyPackage> 1104. Party package1100 illustratively includes a Buyer Party 1106, identified by<BuyerParty> 1108 and </BuyerParty> 1110, and a Seller Party 1112,identified by <SellerParty> 1114 and </SellerParty>, etc.

(d) Relationships

Relationships describe the interdependencies of the entities in thebusiness object model, and are thus an integral part of the businessobject model.

(i) Cardinality of Relationships

FIG. 12 depicts a graphical representation of the cardinalities betweentwo entities. The cardinality between a first entity and a second entityidentifies the number of second entities that could possibly exist foreach first entity. Thus, a 1:c cardinality 1200 between entities A 1202and X 1204 indicates that for each entity A 1202, there is either one orzero 1206 entity X 1204. A 1:1 cardinality 1208 between entities A 1210and X 1212 indicates that for each entity A 1210, there is exactly one1214 entity X 1212. A 1:n cardinality 1216 between entities A 1218 and X1220 indicates that for each entity A 1218, there are one or more 1222entity Xs 1220. A 1:cn cardinality 1224 between entities A 1226 and X1228 indicates that for each entity A 1226, there are any number 1230 ofentity Xs 1228 (i.e., 0 through n Xs for each A).

(ii) Types of Relationships

a. Composition

A composition or hierarchical relationship type is a strong whole-partrelationship which is used to describe the structure within an object.The parts, or dependent entities, represent a semantic refinement orpartition of the whole, or less dependent entity. For example, asdepicted in FIG. 13, the components 1302, wheels 1304, and doors 1306may be combined to form the composite 1300 “Car” 1308 using thecomposition 1310. FIG. 14 depicts a graphical representation of thecomposition 1410 between composite Car 1408 and components wheel 1404and door 1406.

b. Aggregation

An aggregation or an aggregating relationship type is a weak whole-partrelationship between two objects. The dependent object is created by thecombination of one or several less dependent objects. For example, asdepicted in FIG. 15, the properties of a competitor product 1500 aredetermined by a product 1502 and a competitor 1504. A hierarchicalrelationship 1506 exists between the product 1502 and the competitorproduct 1500 because the competitor product 1500 is a component of theproduct 1502. Therefore, the values of the attributes of the competitorproduct 1500 are determined by the product 1502. An aggregatingrelationship 1508 exists between the competitor 1504 and the competitorproduct 1500 because the competitor product 1500 is differentiated bythe competitor 1504. Therefore the values of the attributes of thecompetitor product 1500 are determined by the competitor 1504.

c. Association

An association or a referential relationship type describes arelationship between two objects in which the dependent object refers tothe less dependent object. For example, as depicted in FIG. 16, a person1600 has a nationality, and thus, has a reference to its country 1602 oforigin. There is an association 1604 between the country 1602 and theperson 1600. The values of the attributes of the person 1600 are notdetermined by the country 1602.

(iii) Specialization

Entity types may be divided into subtypes based on characteristics ofthe entity types. For example, FIG. 17 depicts an entity type “vehicle”1700 specialized 1702 into subtypes “truck” 1704, “car” 1706, and “ship”1708. These subtypes represent different aspects or the diversity of theentity type.

Subtypes may be defined based on related attributes. For example,although ships and cars are both vehicles, ships have an attribute,“draft,” that is not found in cars. Subtypes also may be defined basedon certain methods that can be applied to entities of this subtype andthat modify such entities. For example, “drop anchor” can be applied toships. If outgoing relationships to a specific object are restricted toa subset, then a subtype can be defined which reflects this subset.

As depicted in FIG. 18, specializations may further be characterized ascomplete specializations 1800 or incomplete specializations 1802. Thereis a complete specialization 1800 where each entity of the generalizedtype belongs to at least one subtype. With an incomplete specialization1802, there is at least one entity that does not belong to a subtype.Specializations also may be disjoint 1804 or nondisjoint 1806. In adisjoint specialization 1804, each entity of the generalized typebelongs to a maximum of one subtype. With a nondisjoint specialization1806, one entity may belong to more than one subtype. As depicted inFIG. 18, four specialization categories result from the combination ofthe specialization characteristics.

(e) Structural Patterns

(i) Item

An item is an entity type which groups together features of anotherentity type. Thus, the features for the entity type chart of accountsare grouped together to form the entity type chart of accounts item. Forexample, a chart of accounts item is a category of values or value flowsthat can be recorded or represented in amounts of money in accounting,while a chart of accounts is a superordinate list of categories ofvalues or value flows that is defined in accounting.

The cardinality between an entity type and its item is often either 1:nor 1:cn. For example, in the case of the entity type chart of accounts,there is a hierarchical relationship of the cardinality 1:n with theentity type chart of accounts item since a chart of accounts has atleast one item in all cases.

(ii) Hierarchy

A hierarchy describes the assignment of subordinate entities tosuperordinate entities and vice versa, where several entities of thesame type are subordinate entities that have, at most, one directlysuperordinate entity. For example, in the hierarchy depicted in FIG. 19,entity B 1902 is subordinate to entity A 1900, resulting in therelationship (A,B) 1912. Similarly, entity C 1904 is subordinate toentity A 1900, resulting in the relationship (A,C) 1914. Entity D 1906and entity E 1908 are subordinate to entity B 1902, resulting in therelationships (B,D) 1916 and (B,E) 1918, respectively. Entity F 1910 issubordinate to entity C 1904, resulting in the relationship (C,F) 1920.

Because each entity has at most one superordinate entity, thecardinality between a subordinate entity and its superordinate entity is1:c. Similarly, each entity may have 0, 1 or many subordinate entities.Thus, the cardinality between a superordinate entity and its subordinateentity is 1:cn. FIG. 20 depicts a graphical representation of a ClosingReport Structure Item hierarchy 2000 for a Closing Report Structure Item2002. The hierarchy illustrates the 1:c cardinality 2004 between asubordinate entity and its superordinate entity, and the 1:cncardinality 2006 between a superordinate entity and its subordinateentity.

3. Creation of the Business Object Model

FIGS. 21A-B depict the steps performed using methods and systemsconsistent with the subject matter described herein to create a businessobject model. Although some steps are described as being performed by acomputer, these steps may alternatively be performed manually, orcomputer-assisted, or any combination thereof. Likewise, although somesteps are described as being performed by a computer, these steps mayalso be computer-assisted, or performed manually, or any combinationthereof.

As discussed above, the designers create message choreographies thatspecify the sequence of messages between business entities during atransaction. After identifying the messages, the developers identify thefields contained in one of the messages (step 2100, FIG. 21A). Thedesigners then determine whether each field relates to administrativedata or is part of the object (step 2102). Thus, the first eleven fieldsidentified below in the left column are related to administrative data,while the remaining fields are part of the object.

MessageID Admin ReferenceID CreationDate SenderID AdditionalSenderIDContactPersonID SenderAddress RecipientID AdditionalRecipientIDContactPersonID RecipientAddress ID Main Object AdditionalID PostingDateLastChangeDate AcceptanceStatus Note CompleteTransmission IndicatorBuyer BuyerOrganisationName Person Name FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBox Postal Code Company Postal Code CityName DistrictName PO Box ID PO Box Indicator PO Box Country Code PO BoxRegion Code PO Box City Name Street Name House ID Building ID Floor IDRoom ID Care Of Name AddressDescription Telefonnumber MobileNumberFacsimile Email Seller SellerAddress Location LocationTypeDeliveryItemGroupID DeliveryPriority DeliveryCondition TransferLocationNumberofPartialDelivery QuantityTolerance MaximumLeadTimeTransportServiceLevel TranportCondition TransportDescriptionCashDiscountTerms PaymentForm PaymentCardID PaymentCardReferenceIDSequenceID Holder ExpirationDate AttachmentID AttachmentFilenameDescriptionofMessage ConfirmationDescriptionof Message FollowUpActivityItemID ParentItemID HierarchyType ProductID ProductType ProductNoteProductCategoryID Amount BaseQuantity ConfirmedAmountConfirmedBaseQuantity ItemBuyer ItemBuyerOrganisationName Person NameFunctionalTitle DepartmentName CountryCode StreetPostalCode POBox PostalCode Company Postal Code City Name DistrictName PO Box ID PO BoxIndicator PO Box Country Code PO Box Region Code PO Box City Name StreetName House ID Building ID Floor ID Room ID Care Of NameAddressDescription Telefonnumber MobilNumber Facsimile Email ItemSellerItemSellerAddress ItemLocation ItemLocationType ItemDeliveryItemGroupIDItemDeliveryPriority ItemDeliveryCondition ItemTransferLocationItemNumberofPartialDelivery ItemQuantityTolerance ItemMaximumLeadTimeItemTransportServiceLevel ItemTranportCondition ItemTransportDescriptionContractReference QuoteReference CatalogueReference ItemAttachmentIDItemAttachmentFilename ItemDescription ScheduleLineID DeliveryPeriodQuantity ConfirmedScheduleLineID ConfirmedDeliveryPeriodConfirmedQuantity

Next, the designers determine the proper name for the object accordingto the ISO 11179 naming standards (step 2104). In the example above, theproper name for the “Main Object” is “Purchase Order.” After naming theobject, the system that is creating the business object model determineswhether the object already exists in the business object model (step2106). If the object already exists, the system integrates newattributes from the message into the existing object (step 2108), andthe process is complete.

If at step 2106 the system determines that the object does not exist inthe business object model, the designers model the internal objectstructure (step 2110). To model the internal structure, the designersdefine the components. For the above example, the designers may definethe components identified below.

ID Pur- AdditionalID chase PostingDate Order LastChangeDateAcceptanceStatus Note CompleteTransmission Indicator Buyer BuyerBuyerOrganisationName Person Name FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBox Postal Code Company Postal Code CityName DistrictName PO Box ID PO Box Indicator PO Box Country Code PO BoxRegion Code PO Box City Name Street Name House ID Building ID Floor IDRoom ID Care Of Name AddressDescription Telefonnumber MobileNumberFacsimile Email Seller Seller SellerAddress Location LocationLocationType DeliveryItemGroupID DeliveryTerms DeliveryPriorityDeliveryCondition TransferLocation NumberofPartialDeliveryQuantityTolerance MaximumLeadTime TransportServiceLevelTranportCondition TransportDescription CashDiscountTerms PaymentFormPayment PaymentCardID PaymentCardReferenceID SequenceID HolderExpirationDate AttachmentID AttachmentFilename DescriptionofMessageConfirmationDescriptionof Message FollowUpActivity ItemID Purchase OrderParentItemID Item HierarchyType ProductID Product ProductTypeProductNote ProductCategoryID ProductCategory Amount BaseQuantityConfirmedAmount ConfirmedBaseQuantity ItemBuyer BuyerItemBuyerOrganisation Name Person Name FunctionalTitle DepartmentNameCountryCode StreetPostalCode POBox Postal Code Company Postal Code CityName DistrictName PO Box ID PO Box Indicator PO Box Country Code PO BoxRegion Code PO Box City Name Street Name House ID Building ID Floor IDRoom ID Care Of Name AddressDescription Telefonnumber MobilNumberFacsimile Email ItemSeller Seller ItemSellerAddress ItemLocationLocation ItemLocationType ItemDeliveryItemGroupID ItemDeliveryPriorityItemDeliveryCondition ItemTransferLocation ItemNumberofPartial DeliveryItemQuantityTolerance ItemMaximumLeadTime ItemTransportServiceLevelItemTranportCondition ItemTransportDescription ContractReferenceContract QuoteReference Quote CatalogueReference CatalogueItemAttachmentID ItemAttachmentFilename ItemDescription ScheduleLineIDDeliveryPeriod Quantity ConfirmedScheduleLineID ConfirmedDeliveryPeriodConfirmedQuantity

During the step of modeling the internal structure, the designers alsomodel the complete internal structure by identifying the compositions ofthe components and the corresponding cardinalities, as shown below.

PurchaseOrder 1 Buyer 0 . . . 1 Address 0 . . . 1 ContactPerson 0 . . .1 Address 0 . . . 1 Seller 0 . . . 1 Location 0 . . . 1 Address 0 . . .1 DeliveryTerms 0 . . . 1 Incoterms 0 . . . 1 PartialDelivery 0 . . . 1QuantityTolerance 0 . . . 1 Transport 0 . . . 1 CashDiscount 0 . . . 1Terms MaximumCashDiscount 0 . . . 1 NormalCashDiscount 0 . . . 1PaymentForm 0 . . . 1 PaymentCard 0 . . . 1 Attachment 0 . . . nDescription 0 . . . 1 Confirmation 0 . . . 1 Description Item 0 . . . nHierarchyRelationship 0 . . . 1 Product 0 . . . 1 ProductCategory 0 . .. 1 Price 0 . . . 1 NetunitPrice 0 . . . 1 ConfirmedPrice 0 . . . 1NetunitPrice 0 . . . 1 Buyer 0 . . . 1 Seller 0 . . . 1 Location 0 . . .1 DeliveryTerms 0 . . . 1 Attachment 0 . . . n Description 0 . . . 1ConfirmationDescription 0 . . . 1 ScheduleLine 0 . . . n DeliveryPeriod1 ConfirmedScheduleLine 0 . . . n

After modeling the internal object structure, the developers identifythe subtypes and generalizations for all objects and components (step2112). For example, the Purchase Order may have subtypes Purchase OrderUpdate, Purchase Order Cancellation and Purchase Order Information.Purchase Order Update may include Purchase Order Request, Purchase OrderChange, and Purchase Order Confirmation. Moreover, Party may beidentified as the generalization of Buyer and Seller. The subtypes andgeneralizations for the above example are shown below.

Purchase 1 Order PurchaseOrder Update PurchaseOrder RequestPurchaseOrder Change PurchaseOrder Confirmation PurchaseOrderCancellation PurchaseOrder Information Party BuyerParty 0 . . . 1Address 0 . . . 1 ContactPerson 0 . . . 1 Address 0 . . . 1 SellerParty0 . . . 1 Location ShipToLocation 0 . . . 1 Address 0 . . . 1ShipFromLocation 0 . . . 1 Address 0 . . . 1 DeliveryTerms 0 . . . 1Incoterms 0 . . . 1 PartialDelivery 0 . . . 1 QuantityTolerance 0 . . .1 Transport 0 . . . 1 CashDiscount 0 . . . 1 Terms MaximumCash Discount0 . . . 1 NormalCashDiscount 0 . . . 1 PaymentForm 0 . . . 1 PaymentCard0 . . . 1 Attachment 0 . . . n Description 0 . . . 1 Confirmation 0 . .. 1 Description Item 0 . . . n HierarchyRelationship 0 . . . 1 Product 0. . . 1 ProductCategory 0 . . . 1 Price 0 . . . 1 NetunitPrice 0 . . . 1ConfirmedPrice 0 . . . 1 NetunitPrice 0 . . . 1 Party BuyerParty 0 . . .1 SellerParty 0 . . . 1 Location ShipTo 0 . . . 1 Location ShipFrom 0 .. . 1 Location DeliveryTerms 0 . . . 1 Attachment 0 . . . n Description0 . . . 1 Confirmation 0 . . . 1 Description ScheduleLine 0 . . . nDelivery 1 Period ConfirmedScheduleLine 0 . . . n

After identifying the subtypes and generalizations, the developersassign the attributes to these components (step 2114). The attributesfor a portion of the components are shown below.

Purchase 1 Order ID 1 SellerID 0 . . . 1 BuyerPosting 0 . . . 1 DateTimeBuyerLast 0 . . . 1 ChangeDate Time SellerPosting 0 . . . 1 DateTimeSellerLast 0 . . . 1 ChangeDate Time Acceptance 0 . . . 1 StatusCodeNote 0 . . . 1 ItemList 0 . . . 1 Complete Transmission IndicatorBuyerParty 0 . . . 1 StandardID 0 . . . n BuyerID 0 . . . 1 SellerID 0 .. . 1 Address 0 . . . 1 ContactPerson 0 . . . 1 BuyerID 0 . . . 1SellerID 0 . . . 1 Address 0 . . . 1 SellerParty 0 . . . 1 Product 0 . .. 1 RecipientParty VendorParty 0 . . . 1 Manufacturer 0 . . . 1 PartyBillToParty 0 . . . 1 PayerParty 0 . . . 1 CarrierParty 0 . . . 1 ShipTo0 . . . 1 Location StandardID 0 . . . n BuyerID 0 . . . 1 SellerID 0 . .. 1 Address 0 . . . 1 ShipFrom 0 . . . 1 Location

The system then determines whether the component is one of the objectnodes in the business object model (step 2116, FIG. 21B). If the systemdetermines that the component is one of the object nodes in the businessobject model, the system integrates a reference to the correspondingobject node from the business object model into the object (step 2118).In the above example, the system integrates the reference to the Buyerparty represented by an ID and the reference to the ShipToLocationrepresented by an into the object, as shown below. The attributes thatwere formerly located in the PurchaseOrder object are now assigned tothe new found object party. Thus, the attributes are removed from thePurchaseOrder object.

PurchaseOrder ID SellerID BuyerPostingDateTime BuyerLastChangeDateTimeSellerPostingDateTime SellerLastChangeDateTime AcceptanceStatusCode NoteItemListComplete TransmissionIndicator BuyerParty ID SellerPartyProductRecipientParty VendorParty ManufacturerParty BillToPartyPayerParty CarrierParty ShipToLocation ID ShipFromLocation

During the integration step, the designers classify the relationship(i.e., aggregation or association) between the object node and theobject being integrated into the business object model. The system alsointegrates the new attributes into the object node (step 2120). If atstep 2116, the system determines that the component is not in thebusiness object model, the system adds the component to the businessobject model (step 2122).

Regardless of whether the component was in the business object model atstep 2116, the next step in creating the business object model is to addthe integrity rules (step 2124). There are several levels of integrityrules and constraints which should be described. These levels includeconsistency rules between attributes, consistency rules betweencomponents, and consistency rules to other objects. Next, the designersdetermine the services offered, which can be accessed via interfaces(step 2126). The services offered in the example above includePurchaseOrderCreateRequest, PurchaseOrderCancellationRequest, andPurchaseOrderReleaseRequest. The system then receives an indication ofthe location for the object in the business object model (step 2128).After receiving the indication of the location, the system integratesthe object into the business object model (step 2130).

4. Structure of the Business Object Model

The business object model, which serves as the basis for the process ofgenerating consistent interfaces, includes the elements contained withinthe interfaces. These elements are arranged in a hierarchical structurewithin the business object model.

5. Interfaces Derived from Business Object Model

Interfaces are the starting point of the communication between twobusiness entities. The structure of each interface determines how onebusiness entity communicates with another business entity. The businessentities may act as a unified whole when, based on the businessscenario, the business entities know what an interface contains from abusiness perspective and how to fill the individual elements or fieldsof the interface. As illustrated in FIG. 27A, communication betweencomponents takes place via messages that contain business documents(e.g., business document 27002). The business document 27002 ensures aholistic business-related understanding for the recipient of themessage. The business documents are created and accepted or consumed byinterfaces, specifically by inbound and outbound interfaces. Theinterface structure and, hence, the structure of the business documentare derived by a mapping rule. This mapping rule is known as“hierarchization.” An interface structure thus has a hierarchicalstructure created based on the leading business object 27000. Theinterface represents a usage-specific, hierarchical view of theunderlying usage-neutral object model.

As illustrated in FIG. 27B, several business document objects 27006,27008, and 27010 as overlapping views may be derived for a given leadingobject 27004. Each business document object results from the objectmodel by hierarchization.

To illustrate the hierarchization process, FIG. 27C depicts an exampleof an object model 27012 (i.e., a portion of the business object model)that is used to derive a service operation signature (business documentobject structure). As depicted, leading object X 27014 in the objectmodel 27012 is integrated in a net of object A 27016, object B 27018,and object C 27020. Initially, the parts of the leading object 27014that are required for the business object document are adopted. In onevariation, all parts required for a business document object are adoptedfrom leading object 27014 (making such an operation a maximal serviceoperation). Based on these parts, the relationships to the superordinateobjects (i.e., objects A, B, and C from which object X depends) areinverted. In other words, these objects are adopted as dependent orsubordinate objects in the new business document object.

For example, object A 27016, object B 27018, and object C 27020 haveinformation that characterize object X. Because object A 27016, object B27018, and object C 27020 are superordinate to leading object X 27014,the dependencies of these relationships change so that object A 27016,object B 27018, and object C 27020 become dependent and subordinate toleading object X 27014. This procedure is known as “derivation of thebusiness document object by hierarchization.”

Business-related objects generally have an internal structure (parts).This structure can be complex and reflect the individual parts of anobject and their mutual dependency. When creating the operationsignature, the internal structure of an object is strictly hierarchized.Thus, dependent parts keep their dependency structure, and relationshipsbetween the parts within the object that do not represent thehierarchical structure are resolved by prioritizing one of therelationships.

Relationships of object X to external objects that are referenced andwhose information characterizes object X are added to the operationsignature. Such a structure can be quite complex (see, for example, FIG.27D). The cardinality to these referenced objects is adopted as 1:1 or1:C, respectively. By this, the direction of the dependency changes. Therequired parts of this referenced object are adopted identically, bothin their cardinality and in their dependency arrangement.

The newly created business document object contains all requiredinformation, including the incorporated master data information of thereferenced objects. As depicted in FIG. 27D, components Xi in leadingobject X 27022 are adopted directly. The relationship of object X 27022to object A 27024, object B 27028, and object C 27026 are inverted, andthe parts required by these objects are added as objects that dependfrom object X 27022. As depicted, all of object A 27024 is adopted. B3and B4 are adopted from object B 27028, but B1 is not adopted. Fromobject C 27026, C2 and C1 are adopted, but C3 is not adopted.

FIG. 27E depicts the business document object X 27030 created by thishierarchization process. As shown, the arrangement of the elementscorresponds to their dependency levels, which directly leads to acorresponding representation as an XML structure 27032.

The following provides certain rules that can be adopted singly or incombination with regard to the hierarchization process:

-   -   A business document object always refers to a leading business        document object and is derived from this object.    -   The name of the root entity in the business document entity is        the name of the business object or the name of a specialization        of the business object or the name of a service specific view        onto the business object.    -   The nodes and elements of the business object that are relevant        (according to the semantics of the associated message type) are        contained as entities and elements in the business document        object.    -   The name of a business document entity is predefined by the name        of the corresponding business object node. The name of the        superordinate entity is not repeated in the name of the business        document entity. The “full” semantic name results from the        concatenation of the entity names along the hierarchical        structure of the business document object.    -   The structure of the business document object is, except for        deviations due to hierarchization, the same as the structure of        the business object.    -   The cardinalities of the business document object nodes and        elements are adopted identically or more restrictively to the        business document object.    -   An object from which the leading business object is dependent        can be adopted to the business document object. For this        arrangement, the relationship is inverted, and the object (or        its parts, respectively) are hierarchically subordinated in the        business document object.    -   Nodes in the business object representing generalized business        information can be adopted as explicit entities to the business        document object (generally speaking, multiply TypeCodes out).        When this adoption occurs, the entities are named according to        their more specific semantic (name of TypeCode becomes prefix).        -   Party nodes of the business object are modeled as explicit            entities for each party role in the business document            object. These nodes are given the name <Prefix><Party            Role>Party, for example, BuyerParty, ItemBuyerParty.        -   BTDReference nodes are modeled as separate entities for each            reference type in the business document object. These nodes            are given the name <Qualifier><BO><Node>Reference, for            example SalesOrderReference, OriginSalesOrderReference,            SalesOrderItemReference.        -   A product node in the business object comprises all of the            information on the Product, ProductCategory, and Batch. This            information is modeled in the business document object as            explicit entities for Product, ProductCategory, and Batch.    -   Entities which are connected by a 1:1 relationship as a result        of hierarchization can be combined to a single entity, if they        are semantically equivalent. Such a combination can often occurs        if a node in the business document object that results from an        assignment node is removed because it does not have any        elements.    -   The message type structure is typed with data types.        -   Elements are typed by GDTs according to their business            objects.        -   Aggregated levels are typed with message type specific data            types (Intermediate Data Types), with their names being            built according to the corresponding paths in the message            type structure.        -   The whole message type structured is typed by a message data            type with its name being built according to the root entity            with the suffix “Message”.    -   For the message type, the message category (e.g., information,        notification, query, response, request, confirmation, etc.) is        specified according to the suited transaction communication        pattern.

In one variation, the derivation by hierarchization can be initiated byspecifying a leading business object and a desired view relevant for aselected service operation. This view determines the business documentobject. The leading business object can be the source object, the targetobject, or a third object. Thereafter, the parts of the business objectrequired for the view are determined. The parts are connected to theroot node via a valid path along the hierarchy. Thereafter, one or moreindependent objects (object parts, respectively) referenced by theleading object which are relevant for the service may be determined(provided that a relationship exists between the leading object and theone or more independent objects).

Once the selection is finalized, relevant nodes of the leading objectnode that are structurally identical to the message type structure canthen be adopted. If nodes are adopted from independent objects or objectparts, the relationships to such independent objects or object parts areinverted. Linearization can occur such that a business object nodecontaining certain TypeCodes is represented in the message typestructure by explicit entities (an entity for each value of theTypeCode). The structure can be reduced by checking all 1:1cardinalities in the message type structure. Entities can be combined ifthey are semantically equivalent, one of the entities carries noelements, or an entity solely results from an n:m assignment in thebusiness object.

After the hierarchization is completed, information regardingtransmission of the business document object (e.g.,CompleteTransmissionIndicator, ActionCodes, message category, etc.) canbe added. A standardized message header can be added to the message typestructure and the message structure can be typed. Additionally, themessage category for the message type can be designated.

Invoice Request and Invoice Confirmation are examples of interfaces.These invoice interfaces are used to exchange invoices and invoiceconfirmations between an invoicing party and an invoice recipient (suchas between a seller and a buyer) in a B2B process. Companies can createinvoices in electronic as well as in paper form. Traditional methods ofcommunication, such as mail or fax, for invoicing are cost intensive,prone to error, and relatively slow, since the data is recordedmanually. Electronic communication eliminates such problems. Themotivating business scenarios for the Invoice Request and InvoiceConfirmation interfaces are the Procure to Stock (PTS) and Sell fromStock (SFS) scenarios. In the PTS scenario, the parties use invoiceinterfaces to purchase and settle goods. In the SFS scenario, theparties use invoice interfaces to sell and invoice goods. The invoiceinterfaces directly integrate the applications implementing them andalso form the basis for mapping data to widely-used XML standard formatssuch as RosettaNet, PIDX, xCBL, and CIDX.

The invoicing party may use two different messages to map a B2Binvoicing process: (1) the invoicing party sends the message typeInvoiceRequest to the invoice recipient to start a new invoicingprocess; and (2) the invoice recipient sends the message typeInvoiceConfirmation to the invoicing party to confirm or reject anentire invoice or to temporarily assign it the status “pending.”

An InvoiceRequest is a legally binding notification of claims orliabilities for delivered goods and rendered services—usually, a paymentrequest for the particular goods and services. The message typeInvoiceRequest is based on the message data type InvoiceMessage. TheInvoiceRequest message (as defined) transfers invoices in the broadersense. This includes the specific invoice (request to settle aliability), the debit memo, and the credit memo.

InvoiceConfirmation is a response sent by the recipient to the invoicingparty confirming or rejecting the entire invoice received or statingthat it has been assigned temporarily the status “pending.” The messagetype InvoiceConfirmation is based on the message data typeInvoiceMessage. An InvoiceConfirmation is not mandatory in a B2Binvoicing process, however, it automates collaborative processes anddispute management.

Usually, the invoice is created after it has been confirmed that thegoods were delivered or the service was provided. The invoicing party(such as the seller) starts the invoicing process by sending anInvoiceRequest message. Upon receiving the InvoiceRequest message, theinvoice recipient (for instance, the buyer) can use theInvoiceConfirmation message to completely accept or reject the invoicereceived or to temporarily assign it the status “pending.” TheInvoiceConfirmation is not a negotiation tool (as is the case in ordermanagement), since the options available are either to accept or rejectthe entire invoice. The invoice data in the InvoiceConfirmation messagemerely confirms that the invoice has been forwarded correctly and doesnot communicate any desired changes to the invoice. Therefore, theInvoiceConfirmation includes the precise invoice data that the invoicerecipient received and checked. If the invoice recipient rejects aninvoice, the invoicing party can send a new invoice after checking thereason for rejection (AcceptanceStatus and ConfirmationDescription atInvoice and InvoiceItem level). If the invoice recipient does notrespond, the invoice is generally regarded as being accepted and theinvoicing party can expect payment.

FIGS. 22A-F depict a flow diagram of the steps performed by methods andsystems consistent with the subject matter described herein to generatean interface from the business object model. Although described as beingperformed by a computer, these steps may alternatively be performedmanually, or using any combination thereof. The process begins when thesystem receives an indication of a package template from the designer,i.e., the designer provides a package template to the system (step2200).

Package templates specify the arrangement of packages within a businesstransaction document. Package templates are used to define the overallstructure of the messages sent between business entities. Methods andsystems consistent with the subject matter described herein use packagetemplates in conjunction with the business object model to derive theinterfaces.

The system also receives an indication of the message type from thedesigner (step 2202). The system selects a package from the packagetemplate (step 2204), and receives an indication from the designerwhether the package is required for the interface (step 2206). If thepackage is not required for the interface, the system removes thepackage from the package template (step 2208). The system then continuesthis analysis for the remaining packages within the package template(step 2210).

If, at step 2206, the package is required for the interface, the systemcopies the entity template from the package in the business object modelinto the package in the package template (step 2212, FIG. 22B). Thesystem determines whether there is a specialization in the entitytemplate (step 2214). If the system determines that there is aspecialization in the entity template, the system selects a subtype forthe specialization (step 2216). The system may either select the subtypefor the specialization based on the message type, or it may receive thisinformation from the designer. The system then determines whether thereare any other specializations in the entity template (step 2214). Whenthe system determines that there are no specializations in the entitytemplate, the system continues this analysis for the remaining packageswithin the package template (step 2210, FIG. 22A).

At step 2210, after the system completes its analysis for the packageswithin the package template, the system selects one of the packagesremaining in the package template (step 2218, FIG. 22C), and selects anentity from the package (step 2220). The system receives an indicationfrom the designer whether the entity is required for the interface (step2222). If the entity is not required for the interface, the systemremoves the entity from the package template (step 2224). The systemthen continues this analysis for the remaining entities within thepackage (step 2226), and for the remaining packages within the packagetemplate (step 2228).

If, at step 2222, the entity is required for the interface, the systemretrieves the cardinality between a superordinate entity and the entityfrom the business object model (step 2230, FIG. 22D). The system alsoreceives an indication of the cardinality between the superordinateentity and the entity from the designer (step 2232). The system thendetermines whether the received cardinality is a subset of the businessobject model cardinality (step 2234). If the received cardinality is nota subset of the business object model cardinality, the system sends anerror message to the designer (step 2236). If the received cardinalityis a subset of the business object model cardinality, the system assignsthe received cardinality as the cardinality between the superordinateentity and the entity (step 2238). The system then continues thisanalysis for the remaining entities within the package (step 2226, FIG.22C), and for the remaining packages within the package template (step2228).

The system then selects a leading object from the package template (step2240, FIG. 22E). The system determines whether there is an entitysuperordinate to the leading object (step 2242). If the systemdetermines that there is an entity superordinate to the leading object,the system reverses the direction of the dependency (step 2244) andadjusts the cardinality between the leading object and the entity (step2246). The system performs this analysis for entities that aresuperordinate to the leading object (step 2242). If the systemdetermines that there are no entities superordinate to the leadingobject, the system identifies the leading object as analyzed (step2248).

The system then selects an entity that is subordinate to the leadingobject (step 2250, FIG. 22F). The system determines whether anynon-analyzed entities are superordinate to the selected entity (step2252). If a non-analyzed entity is superordinate to the selected entity,the system reverses the direction of the dependency (step 2254) andadjusts the cardinality between the selected entity and the non-analyzedentity (step 2256). The system performs this analysis for non-analyzedentities that are superordinate to the selected entity (step 2252). Ifthe system determines that there are no non-analyzed entitiessuperordinate to the selected entity, the system identifies the selectedentity as analyzed (step 2258), and continues this analysis for entitiesthat are subordinate to the leading object (step 2260). After thepackages have been analyzed, the system substitutes theBusinessTransactionDocument (“BTD”) in the package template with thename of the interface (step 2262). This includes the “BTD” in theBTDItem package and the “BTD” in the BTDItemScheduleLine package.

6. Use of an Interface

The XI stores the interfaces (as an interface type). At runtime, thesending party's program instantiates the interface to create a businessdocument, and sends the business document in a message to the recipient.The messages are preferably defined using XML. In the example depictedin FIG. 23, the Buyer 2300 uses an application 2306 in its system toinstantiate an interface 2308 and create an interface object or businessdocument object 2310. The Buyer's application 2306 uses data that is inthe sender's component-specific structure and fills the businessdocument object 2310 with the data. The Buyer's application 2306 thenadds message identification 2312 to the business document and places thebusiness document into a message 2302. The Buyer's application 2306sends the message 2302 to the Vendor 2304. The Vendor 2304 uses anapplication 2314 in its system to receive the message 2302 and store thebusiness document into its own memory. The Vendor's application 2314unpacks the message 2302 using the corresponding interface 2316 storedin its XI to obtain the relevant data from the interface object orbusiness document object 2318.

From the component's perspective, the interface is represented by aninterface proxy 2400, as depicted in FIG. 24. The proxies 2400 shieldthe components 2402 of the sender and recipient from the technicaldetails of sending messages 2404 via XI. In particular, as depicted inFIG. 25, at the sending end, the Buyer 2500 uses an application 2510 inits system to call an implemented method 2512, which generates theoutbound proxy 2506. The outbound proxy 2506 parses the internal datastructure of the components and converts them to the XML structure inaccordance with the business document object. The outbound proxy 2506packs the document into a message 2502. Transport, routing and mappingthe XML message to the recipient 28304 is done by the routing system(XI, modeling environment 516, etc.).

When the message arrives, the recipient's inbound proxy 2508 calls itscomponent-specific method 2514 for creating a document. The proxy 2508at the receiving end downloads the data and converts the XML structureinto the internal data structure of the recipient component 2504 forfurther processing.

As depicted in FIG. 26A, a message 2600 includes a message header 2602and a business document 2604. The message 2600 also may include anattachment 2606. For example, the sender may attach technical drawings,detailed specifications or pictures of a product to a purchase order forthe product. The business document 2604 includes a business documentmessage header 2608 and the business document object 2610. The businessdocument message header 2608 includes administrative data, such as themessage ID and a message description. As discussed above, the structure2612 of the business document object 2610 is derived from the businessobject model 2614. Thus, there is a strong correlation between thestructure of the business document object and the structure of thebusiness object model. The business document object 2610 forms the coreof the message 2600.

In collaborative processes as well as Q&A processes, messages shouldrefer to documents from previous messages. A simple business documentobject ID or object ID is insufficient to identify individual messagesuniquely because several versions of the same business document objectcan be sent during a transaction. A business document object ID with aversion number also is insufficient because the same version of abusiness document object can be sent several times. Thus, messagesrequire several identifiers during the course of a transaction.

As depicted in FIG. 26B, the message header 2618 in message 2616includes a technical ID (“ID4”) 2622 that identifies the address for acomputer to route the message. The sender's system manages the technicalID 2622.

The administrative information in the business document message header2624 of the payload or business document 2620 includes aBusinessDocumentMessageID (“ID3”) 2628. The business entity or component2632 of the business entity manages and sets theBusinessDocumentMessageID 2628. The business entity or component 2632also can refer to other business documents using theBusinessDocumentMessageID 2628. The receiving component 2632 requires noknowledge regarding the structure of this ID. TheBusinessDocumentMessageID 2628 is, as an ID, unique. Creation of amessage refers to a point in time. No versioning is typically expressedby the ID. Besides the BusinessDocumentMessageID 2628, there also is abusiness document object ID 2630, which may include versions.

The component 2632 also adds its own component object ID 2634 when thebusiness document object is stored in the component. The componentobject ID 2634 identifies the business document object when it is storedwithin the component. However, not all communication partners may beaware of the internal structure of the component object ID 2634. Somecomponents also may include a versioning in their ID 2634.

7. Use of Interfaces Across Industries

Methods and systems consistent with the subject matter described hereinprovide interfaces that may be used across different business areas fordifferent industries. Indeed, the interfaces derived using methods andsystems consistent with the subject matter described herein may bemapped onto the interfaces of different industry standards. Unlike theinterfaces provided by any given standard that do not include theinterfaces required by other standards, methods and systems consistentwith the subject matter described herein provide a set of consistentinterfaces that correspond to the interfaces provided by differentindustry standards. Due to the different fields provided by eachstandard, the interface from one standard does not easily map ontoanother standard. By comparison, to map onto the different industrystandards, the interfaces derived using methods and systems consistentwith the subject matter described herein include most of the fieldsprovided by the interfaces of different industry standards. Missingfields may easily be included into the business object model. Thus, byderivation, the interfaces can be extended consistently by these fields.Thus, methods and systems consistent with the subject matter describedherein provide consistent interfaces or services that can be used acrossdifferent industry standards.

For example, FIG. 28 illustrates an example method 2800 for serviceenabling. In this example, the enterprise services infrastructure mayoffer one common and standard-based service infrastructure. Further, onecentral enterprise services repository may support uniform servicedefinition, implementation and usage of services for user interface, andcross-application communication. In step 2801, a business object isdefined via a process component model in a process modeling phase. Next,in step 2802, the business object is designed within an enterpriseservices repository. For example, FIG. 29 provides a graphicalrepresentation of one of the business objects 2900. As shown, aninnermost layer or kernel 2901 of the business object may represent thebusiness object's inherent data. Inherent data may include, for example,an employee's name, age, status, position, address, etc. A second layer2902 may be considered the business object's logic. Thus, the layer 2902includes the rules for consistently embedding the business object in asystem environment as well as constraints defining values and domainsapplicable to the business object. For example, one such constraint maylimit sale of an item only to a customer with whom a company has abusiness relationship. A third layer 2903 includes validation optionsfor accessing the business object. For example, the third layer 2903defines the business object's interface that may be interfaced by otherbusiness objects or applications. A fourth layer 2904 is the accesslayer that defines technologies that may externally access the businessobject.

Accordingly, the third layer 2903 separates the inherent data of thefirst layer 2901 and the technologies used to access the inherent data.As a result of the described structure, the business object reveals onlyan interface that includes a set of clearly defined methods. Thus,applications access the business object via those defined methods. Anapplication wanting access to the business object and the dataassociated therewith usually includes the information or data to executethe clearly defined methods of the business object's interface. Suchclearly defined methods of the business object's interface represent thebusiness object's behavior. That is, when the methods are executed, themethods may change the business object's data. Therefore, an applicationmay utilize any business object by providing the information or datawithout having any concern for the details related to the internaloperation of the business object. Returning to method 2800, a serviceprovider class and data dictionary elements are generated within adevelopment environment at step 2803. In step 2804, the service providerclass is implemented within the development environment.

FIG. 30 illustrates an example method 3000 for a process agentframework. For example, the process agent framework may be the basicinfrastructure to integrate business processes located in differentdeployment units. It may support a loose coupling of these processes bymessage based integration. A process agent may encapsulate the processintegration logic and separate it from business logic of businessobjects. As shown in FIG. 30, an integration scenario and a processcomponent interaction model are defined during a process modeling phasein step 3001. In step 3002, required interface operations and processagents are identified during the process modeling phase also. Next, instep 3003, a service interface, service interface operations, and therelated process agent are created within an enterprise servicesrepository as defined in the process modeling phase. In step 3004, aproxy class for the service interface is generated. Next, in step 3005,a process agent class is created and the process agent is registered. Instep 3006, the agent class is implemented within a developmentenvironment.

FIG. 31 illustrates an example method 3100 for status and actionmanagement (S&AM). For example, status and action management maydescribe the life cycle of a business object (node) by defining actionsand statuses (as their result) of the business object (node), as wellas, the constraints that the statuses put on the actions. In step 3101,the status and action management schemas are modeled per a relevantbusiness object node within an enterprise services repository. In step3102, existing statuses and actions from the business object model areused or new statuses and actions are created. Next, in step 3103, theschemas are simulated to verify correctness and completeness. In step3104, missing actions, statuses, and derivations are created in thebusiness object model with the enterprise services repository.Continuing with method 3100, the statuses are related to correspondingelements in the node in step 3105. In step 3106, status code GDT's aregenerated, including constants and code list providers. Next, in step3107, a proxy class for a business object service provider is generatedand the proxy class S&AM schemas are imported. In step 3108, the serviceprovider is implemented and the status and action management runtimeinterface is called from the actions.

Regardless of the particular hardware or software architecture used, thedisclosed systems or software are generally capable of implementingbusiness objects and deriving (or otherwise utilizing) consistentinterfaces that are suitable for use across industries, acrossbusinesses, and across different departments within a business inaccordance with some or all of the following description. In short,system 100 contemplates using any appropriate combination andarrangement of logical elements to implement some or all of thedescribed functionality.

Moreover, the preceding flowcharts and accompanying descriptionillustrate example methods. The present services environmentcontemplates using or implementing any suitable technique for performingthese and other tasks. It will be understood that these methods are forillustration purposes only and that the described or similar techniquesmay be performed at any appropriate time, including concurrently,individually, or in combination. In addition, many of the steps in theseflowcharts may take place simultaneously and/or in different orders thanas shown. Moreover, the services environment may use methods withadditional steps, fewer steps, and/or different steps, so long as themethods remain appropriate.

Individual Bill of Material Interfaces

An Individual Material Bill Of Material is a list that includes elementsused to define and describe components that are used to assemble anindividual material. The IndividualMaterialBillOfMaterial interfaceperforms anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryResponse_Inoperation.

TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryResponse_Inis a query to and response from Product Data Maintenance to supplyvariant data to a user. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryResponse_Incan allow clerks to use the inbound operation Find Individual MaterialBill Of Material Variant By Variant Identifying Elements to displayvariant data of an Individual Material Bill Of Material. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryResponse_Inoperation includes various message types, namely anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQuery_syncand anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponse_sync.The structure of theIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQuery_syncmessage type is specified by anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_syncmessage data type. The structure of theIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponse_syncmessage type is specified by anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_syncmessage data type.

The message choreography of FIG. 32 describes a possible logicalsequence of messages that can be used to realize an Individual Bill ofMaterial business scenario.

A “Clerk” system 32000 can query to display variant data of anIndividual Material Bill of Material using anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQuery_syncmessage 32004 as shown, for example, in FIG. 32. A “Product DataMaintenance” system 32002 can confirm the request using aIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponse_syncmessage 32006 as shown, for example, in FIG. 32.

FIG. 33 illustrates one example logical configuration ofIndividualMaterialBillOfMaterialMessage message 33000. Specifically,this figure depicts the arrangement and hierarchy of various componentssuch as one or more levels of packages, entities, and datatypes, shownhere as 33000 through 33022. As described above, packages may be used torepresent hierarchy levels. Entities are discrete business elements thatare used during a business transaction. Data types are used to typeobject entities and interfaces with a structure. For example,IndividualMaterialBillOfMaterialMessage message 33000 includes, amongother things, IndividualMaterialBillOfMaterial 33014. Accordingly,heterogeneous applications may communicate using this consistent messageconfigured as such.

Additionally, FIG. 34 illustrates one example logical configuration ofIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_syncmessage 34000. Specifically, this figure depicts the arrangement andhierarchy of various components such as one or more levels of packages,entities, and datatypes, shown here as 34000 through 34010. As describedabove, packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example,IndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_syncmessage 34000 includes, among other things, Selection 34004.Accordingly, heterogeneous applications may communicate using thisconsistent message configured as such.

Additionally, FIG. 35 illustrates one example logical configuration ofIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_(—)syncmessage 35000. Specifically, this figure depicts the arrangement andhierarchy of various components such as one or more levels of packages,entities, and datatypes, shown here as 35000 through 35026. As describedabove, packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example,IndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_syncmessage 35000 includes, among other things,IndividualMaterialBillOfMaterial 35004. Accordingly, heterogeneousapplications may communicate using this consistent message configured assuch.

FIGS. 36-1 through 36-7 show an IndividualMaterialBillOfMaterialMessage36000 package. The IndividualMaterialBillOfMaterialMessage 36000 packageincludes an IndividualMaterialBillOfMaterialMessage 36002 entity. TheIndividualMaterialBillOfMaterialMessage 36000 package includes variouspackages, namely a MessageHeader 36004 package and anIndividualMaterialBillOfMaterial 36010 package.

The MessageHeader 36004 package includes a MessageHeader 36006 entity.The MessageHeader 36006 entity is a BusinessDocumentMessageHeader 36008data type.

The IndividualMaterialBillOfMaterial 36010 package includes anIndividualMaterialBillOfMaterial 36012 entity. TheIndividualMaterialBillOfMaterial 36012 entity is anIndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOM 36014 data type. TheIndividualMaterialBillOfMaterial 36010 package includes a Variant 36036package.

The IndividualMaterialBillOfMaterial 36012 entity includes variousattributes, namely an InternalID 36016 attribute, an ID 36020 attribute,an UsageCode 36024 attribute, an UsageName 36028 attribute and aDescription 36032 attribute. The InternalID 36016 attribute is aNOSC_BillOfMaterialInternalID 36018 data type. The ID 36020 attribute isa NOSC_BillOfMaterialID 36022 data type. The UsageCode 36024 attributeis a NOSC_BillOfMaterialUsageCode/BillOfMaterialUsageCode 36026 datatype. The UsageName 36028 attribute is a LEN30_Name 36030 data type. TheDescription 36032 attribute is a SHORT_Description 36034 data type.

The Variant 36036 package includes a Variant 36038 entity. The Variant36038 entity is an IndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOMVar36040 data type. The Variant 36036 package includes an Item 36074package. The Variant 36038 entity includes various attributes, namely anID 36042 attribute, an IndividualMaterialID 36046 attribute, aDescription 36050 attribute, an IndividualMaterialDescription 36054attribute and a ValidityDatePeriod 36058 attribute. The Variant 36038entity includes a Location 36062 subordinate entity. The ID 36042attribute is a BillOfMaterialVariantID 36044 data type. TheIndividualMaterialID 36046 attribute is aProductInternalID/NOSC_ProductInternalID 36048 data type.

The Description 36050 attribute is a SHORT_Description 36052 data type.The IndividualMaterialDescription 36054 attribute is a SHORT_Description36056 data type. The ValidityDatePeriod 36058 attribute is anUPPEROPEN_DatePeriod 36060 data type. The Location 36062 entity includesvarious attributes, namely an InternalID 36066 attribute and a Name36070 attribute. The InternalID 36066 attribute is aNOSC_LocationInternalID 36068 data type. The Name 36070 attribute is aLANGUAGEINDEPENDENT_MEDIUM_Name 36072 data type.

The Item 36074 package includes an Item 36076 entity. The Item 36076entity is an IndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOMVarItm36078 data type. The Item 36076 entity includes an ID 36080 attribute.The Item 36076 entity includes a ChangeState 36084 subordinate entity.The ID 36080 attribute is a BillOfMaterialItemID 36082 data type.

The ChangeState 36084 entity includes various attributes, namely an ID36088 attribute, a MaterialInternalID 36092 attribute, aStartEngineeringChangeOrderID 36096 attribute, anEndEngineeringChangeOrderID 36100 attribute, a ValidityDatePeriod 36104attribute, a LogisticsItemTypeCode 36108 attribute, aLogisticsItemIndexText 36112 attribute, a DesiredQuantity 36116attribute, a QuantityFixedIndicator 36120 attribute, aMaterialDescription 36124 attribute, a Description 36128 attribute and aLogisticsItemTypeName 36132 attribute.

The ID 36088 attribute is a BillOfMaterialItemChangeStateID 36090 datatype. The MaterialInternalID 36092 attribute is aNOSC_ProductInternalID/ProductInternalID 36094 data type. TheStartEngineeringChangeOrderID 36096 attribute is aNOSC_EngineeringChangeOrderID/EngineeringChangeOrderID 36098 data type.The EndEngineeringChangeOrderID 36100 attribute is aNOSC_EngineeringChangeOrderID/EngineeringChangeOrderID 36102 data type.The ValidityDatePeriod 36104 attribute is an UPPEROPEN_DatePeriod 36106data type.

The LogisticsItemTypeCode 36108 attribute is aNOSC_LogisticsItemTypeCode/LogisticsItemTypeCode 36110 data type. TheLogisticsItemIndexText 36112 attribute is a LogisticsItemIndexText 36114data type. The DesiredQuantity 36116 attribute is a Quantity 36118 datatype. The QuantityFixedIndicator 36120 attribute is an Indicator 36122data type. The MaterialDescription 36124 attribute is aSHORT_Description 36126 data type. The Description 36128 attribute is aSHORT_Description 36130 data type. The LogisticsItemTypeName 36132attribute is a LEN30_Name 36134 data type.

FIGS. 37-1 through 37-2 show anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_sync37000 package. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_sync37000 package includes anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQuery_sync37002 entity. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_sync37002 entity is an IndivMatlBOMVarItmByVarIdfgElmntsQryMsg_s 37004 datatype. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsQueryMessage_sync37000 package includes various packages, namely a Selection 37006package and a ProcessingConditions 37040 package.

The Selection 37006 package includes anIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity. The Selection 37008 entity is anIndivMatlBOMVarItmByVarIdfgElmntsQry_sSel 37012 data type.

The IndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity has a cardinality of 1 37010 meaning that for each instanceof the Selection 37006 package there is oneIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity. TheIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity includes various attributes, namely aVariantIndividualMaterialID 37014 attribute, a VariantPlantID 37020attribute, and a VariantValidityDatePeriodStartDate 37026 attribute. TheIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity includes a UsageCode 37032 subordinate entity.

The VariantIndividualMaterialID 37014 attribute is aNOSC_ProductInternalID 37018 data type. The VariantIndividualMaterialID37014 attribute has a cardinality of 1 37016 meaning that for eachinstance of theIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity there is one VariantIndividualMaterialID 37014 attribute.

The VariantPlantID 37020 attribute is a NOSC_PlantID 37024 data type.The VariantPlantID 37020 attribute has a cardinality of 0.1 37022meaning that for each instance of theIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity there may be one VariantPlantID 37020 attribute.

The UsageCode 37032 entity includes a VariantUsageofonlyusage attribute37034. The VariantUsageofonlyusage 37034 attribute is aNOSC_BillOfMaterialUsageCode 37038 data type. TheVariantUsageofonlyusage 37034 attribute has a cardinality of 1 37036meaning that for each instance of the UsageCode 37032 entity there isone VariantUsageofonlyusage 37034 attribute.

The VariantValidityDatePeriodStartDate 37026 attribute has a cardinalityof 0 . . . 1 37028 meaning that for each instance of theIndividualMaterialBillOfMaterialVariantByVariantIdentifyingElements37008 entity there may be one VariantValidityDatePeriodStartDate 37026attribute.

The ProcessingConditions 37040 package includes a ProcessingConditions37042 entity. The ProcessingConditions 37042 entity is aWITHOUT_LASTRETURNED_QueryProcessingConditions 37046 data type. TheProcessingConditions 37042 entity has a cardinality of 0 . . . 1 37044meaning that for each instance of the ProcessingConditions 37040 packagethere may be one ProcessingConditions 37042 entity.

FIGS. 38-1 through 38-7 show anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_sync38000 package. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_sync38000 package includes anIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponse_sync38002 entity. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_sync38002 entity is an IndivMatlBOMVarItmByVarIdfgElmntsRspMsg_s 38004 datatype. TheIndividualMaterialBillOfMaterialERPVariantByVariantIdentifyingElementsResponseMessage_(—)sync38000 package includes various packages, namely anIndividualMaterialBillOfMaterial 38006 package, a ProcessingConditions38192 package and a Log 38200 package.

The IndividualMaterialBillOfMaterial 38006 package includes anIndividualMaterialBillOfMaterial 38008 entity. TheIndividualMaterialBillOfMaterial 38008 entity is anIndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOM 38012 data type. TheIndividualMaterialBillOfMaterial 38006 package includes a Variant 38044package.

The IndividualMaterialBillOfMaterial 38008 entity has a cardinality of 0. . . n 38010 meaning that for each instance of theIndividualMaterialBillOfMaterial 38006 package there may be one or moreIndividualMaterialBillOfMaterial 38008 entities. TheIndividualMaterialBillOfMaterial 38008 entity includes variousattributes, namely an InternalID 38014 attribute, an ID 38020 attribute,an UsageCode 38026 attribute, an UsageName 38032 attribute and aDescription 38038 attribute.

The InternalID 38014 attribute is a NOSC_BillOfMaterialInternalID 38018data type. The InternalID 38014 attribute has a cardinality of 1 38016meaning that for each instance of the IndividualMaterialBillOfMaterial38008 entity there is one InternalID 38014 attribute. The ID 38020attribute is a NOSC_BillOfMaterialID 38024 data type. The ID 38020attribute has a cardinality of 0 . . . 1 38022 meaning that for eachinstance of the IndividualMaterialBillOfMaterial 38008 entity there maybe one ID 38020 attribute.

The UsageCode 38026 attribute is a NOSC_BillOfMaterialUsageCode 38030data type. The UsageCode 38026 attribute has a cardinality of 1 38028meaning that for each instance of the IndividualMaterialBillOfMaterial38008 entity there is one UsageCode 38026 attribute. The UsageName 38032attribute is a LEN30_Name 38036 data type. The UsageName 38032 attributehas a cardinality of 0 . . . 1 38034 meaning that for each instance ofthe IndividualMaterialBillOfMaterial 38008 entity there may be oneUsageName 38032 attribute.

The Description 38038 attribute is a SHORT_Description 38042 data type.The Description 38038 attribute has a cardinality of 0 . . . 1 38040meaning that for each instance of the IndividualMaterialBillOfMaterial38008 entity there may be one Description 38038 attribute.

The Variant 38044 package includes a Variant 38046 entity. The Variant38046 entity is an IndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOMVar38050 data type. The Variant 38044 package includes an Item 38100package.

The Variant 38046 entity has a cardinality of 1 . . . n 38048 meaningthat for each instance of the Variant 38044 package there are one ormore Variant 38046 entities. The Variant 38046 entity includes variousattributes, namely an ID 38052 attribute, an IndividualMaterialID 38058attribute, a Description 38064 attribute, anIndividualMaterialDescription 38070 attribute and a ValidityDatePeriod38076 attribute. The Variant 38046 entity includes a Location 38082subordinate entity.

The ID 38052 attribute is a BillOfMaterialVariantID 38056 data type. TheID 38052 attribute has a cardinality of 1 38054 meaning that for eachinstance of the Variant 38046 entity there is one ID 38052 attribute.The IndividualMaterialID 38058 attribute is a NOSC_ProductInternalID38062 data type. The IndividualMaterialID 38058 attribute has acardinality of 1 38060 meaning that for each instance of the Variant38046 entity there is one IndividualMaterialID 38058 attribute.

The Description 38064 attribute is a SHORT_Description 38068 data type.The Description 38064 attribute has a cardinality of 0 . . . 1 38066meaning that for each instance of the Variant 38046 entity there may beone Description 38064 attribute. The IndividualMaterialDescription 38070attribute is a SHORT_Description 38074 data type. TheIndividualMaterialDescription 38070 attribute has a cardinality of 0 . .. 1 38072 meaning that for each instance of the Variant 38046 entitythere may be one IndividualMaterialDescription 38070 attribute.

The ValidityDatePeriod 38076 attribute is an UPPEROPEN_DatePeriod 38080data type. The ValidityDatePeriod 38076 attribute has a cardinality of 138078 meaning that for each instance of the Variant 38046 entity thereis one ValidityDatePeriod 38076 attribute.

The Location 38082 entity has a cardinality of 0 . . . 1 38084 meaningthat for each instance of the Variant 38046 entity there may be oneLocation 38082 entity. The Location 38082 entity includes variousattributes, namely an InternalID 38088 attribute and a Name 38094attribute. The InternalID 38088 attribute is a NOSC_LocationInternalID38092 data type. The InternalID 38088 attribute has a cardinality of 0 .. . 1 38090 meaning that for each instance of the Location 38082 entitythere may be one InternalID 38088 attribute. The Name 38094 attribute isa LANGUAGEINDEPENDENT_MEDIUM_Name 38098 data type. The Name 38094attribute has a cardinality of 0 . . . 1 38096 meaning that for eachinstance of the Location 38082 entity there may be one Name 38094attribute.

The Item 38100 package includes an Item 38102 entity. The Item 38102entity is an IndivMatlBOMVarItmByVarIdfgElmntsRsp_sIndivMatlBOMVarItm38106 data type. The Item 38102 entity has a cardinality of 0 . . . n38104 meaning that for each instance of the Item 38100 package there maybe one or more Item 38102 entities. The Item 38102 entity includes an ID38108 attribute. The Item 38102 entity includes a ChangeState 38114subordinate entity. The ID 38108 attribute is a BillOfMaterialItemID38112 data type. The ID 38108 attribute has a cardinality of 1 38110meaning that for each instance of the Item 38102 entity there is one ID38108 attribute.

The ChangeState 38114 entity has a cardinality of 1 38116 meaning thatfor each instance of the Item 38102 entity there is one ChangeState38114 entity. The ChangeState 38114 entity includes various attributes,namely an ID 38120 attribute, a MaterialInternalID 38126 attribute, aStartEngineeringChangeOrderID 38132 attribute, anEndEngineeringChangeOrderID 38138 attribute, a ValidityDatePeriod 38144attribute, a LogisticsItemTypeCode 38150 attribute, aLogisticsItemIndexText 38156 attribute, a DesiredQuantity 38162attribute, a QuantityFixedIndicator 38168 attribute, aMaterialDescription 38174 attribute, a Description 38180 attribute and aLogisticsItemTypeName 38186 attribute.

The ID 38120 attribute is a BillOfMaterialItemChangeStateID 38124 datatype. The ID 38120 attribute has a cardinality of 1 38122 meaning thatfor each instance of the ChangeState 38114 entity there is one ID 38120attribute. The MaterialInternalID 38126 attribute is aNOSC_ProductInternalID 38130 data type. The MaterialInternalID 38126attribute has a cardinality of 0 . . . 1 38128 meaning that for eachinstance of the ChangeState 38114 entity there may be oneMaterialInternalID 38126 attribute.

The StartEngineeringChangeOrderID 38132 attribute is aNOSC_EngineeringChangeOrderID 38136 data type. TheStartEngineeringChangeOrderID 38132 attribute has a cardinality of 0 . .. 1 38134 meaning that for each instance of the ChangeState 38114 entitythere may be one StartEngineeringChangeOrderID 38132 attribute.

The EndEngineeringChangeOrderID 38138 attribute is aNOSC_EngineeringChangeOrderID 38142 data type. TheEndEngineeringChangeOrderID 38138 attribute has a cardinality of 0 . . .1 38140 meaning that for each instance of the ChangeState 38114 entitythere may be one EndEngineeringChangeOrderID 38138 attribute. TheValidityDatePeriod 38144 attribute is an UPPEROPEN_DatePeriod 38148 datatype. The ValidityDatePeriod 38144 attribute has a cardinality of 138146 meaning that for each instance of the ChangeState 38114 entitythere is one ValidityDatePeriod 38144 attribute.

The LogisticsItemTypeCode 38150 attribute is aNOSC_LogisticsItemTypeCode 38154 data type. The LogisticsItemTypeCode38150 attribute has a cardinality of 1 38152 meaning that for eachinstance of the ChangeState 38114 entity there is oneLogisticsItemTypeCode 38150 attribute. The LogisticsItemIndexText 38156attribute is a LogisticsItemIndexText 38160 data type. TheLogisticsItemIndexText 38156 attribute has a cardinality of 0 . . . 138158 meaning that for each instance of the ChangeState 38114 entitythere may be one LogisticsItemIndexText 38156 attribute.

The DesiredQuantity 38162 attribute is a Quantity 38166 data type. TheDesiredQuantity 38162 attribute has a cardinality of 0 . . . 1 38164meaning that for each instance of the ChangeState 38114 entity there maybe one DesiredQuantity 38162 attribute. The QuantityFixedIndicator 38168attribute is an Indicator 38172 data type. The QuantityFixedIndicator38168 attribute has a cardinality of 1 38170 meaning that for eachinstance of the ChangeState 38114 entity there is oneQuantityFixedIndicator 38168 attribute.

The MaterialDescription 38174 attribute is a SHORT_Description 38178data type. The MaterialDescription 38174 attribute has a cardinality of0 . . . 1 38176 meaning that for each instance of the ChangeState 38114entity there may be one MaterialDescription 38174 attribute. TheDescription 38180 attribute is a SHORT_Description 38184 data type. TheDescription 38180 attribute has a cardinality of 0 . . . 1 38182 meaningthat for each instance of the ChangeState 38114 entity there may be oneDescription 38180 attribute.

The LogisticsItemTypeName 38186 attribute is a LEN30_Name 38190 datatype. The LogisticsItemTypeName 38186 attribute has a cardinality of 0 .. . 1 38188 meaning that for each instance of the ChangeState 38114entity there may be one LogisticsItemTypeName 38186 attribute.

The ProcessingConditions 38192 package includes a ProcessingConditions38194 entity. The ProcessingConditions 38194 entity is aWITHOUT_LASTRETURNED_ResponseProcessingConditions 38198 data type. TheProcessingConditions 38194 entity has a cardinality of 1 38196 meaningthat for each instance of the ProcessingConditions 38192 package thereis one ProcessingConditions 38194 entity.

The Log 38200 package includes a Log 38202 entity. The Log 38202 entityis a NOSC_Log 38206 data type. The Log 38202 entity has a cardinality of1 38204 meaning that for each instance of the Log 38200 package there isone Log 38202 entity.

Order Tracking View Interfaces

An OrderTrackingView is a document for document information forfollow-on business transactions for tracking and completion of aspecified order. The OrderTrackingView business object includesoperations that can be used to provide appropriate user interfaceinformation for tracking the progress of a specified order (businesstransaction document), by collecting information from related businesstransaction documents. The related business transaction documents can beselected by using A2X (Composite to Application), A2A (Application toApplication), or B2B (Business to Business). In an example where aspecified order is a purchase order of a customer, related documents area sales order and outbound delivery on the supplier side (B2B scenario).The OrderTrackingView interface performs aPurchaseOrderTrackingViewERPByPurchaseOrderQueryResponse_In operation.

The PurchaseOrderTrackingViewERPByPurchaseOrderQueryResponse_In is aquery to and response from BusinessDocumentFlowProcessing to track thestatus of a specified purchase order by using follow-on documents andtheir processing status. The OrderTrackingView for the purchase ordertracks the status of a purchase order in a third-party system. ThePurchaseOrderTrackingViewERPByPurchaseOrderQueryResponse_In operationaccesses a related sales order and outbound delivery on the third-partyside. The PurchaseOrderTrackingViewERPByPurchaseOrderQueryResponse_Inoperation includes various message types, namely aPurchaseOrderTrackingViewERPByPurchaseOrderQuery_sync and aPurchaseOrderTrackingViewERPByPurchaseOrderResponse_sync. The structureof the PurchaseOrderTrackingViewERPByPurchaseOrderQuery_sync messagetype is specified by aPurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync messagedata type. The structure of thePurchaseOrderTrackingViewERPByPurchaseOrderResponse_sync message type isspecified by aPurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync messagedata type.

FIG. 39 describes an example Business Document Flow Processing processcomponent 39000 that can provide interfaces for Order Tracking View. Forexample, the Business Document Flow Processing process component 39000can receive a Purchase Order Tracking View ERP by Purchase Order Querymessage 39002. The message 39002 can be received in a Read OrderTracking View of Purchase Order operation 39008. The operation 39008 canbe included in a Purchase Order Tracking View In interface 39006. Theoperation 39008 can update an Order Tracking View business object 39010.Upon completion, the operation 39008 can send a Purchase Order TrackingView ERP by Purchase Order Response message 39004.

FIG. 40 illustrates one example logical configuration ofPurchaseOrderTrackingViewERPByPurchaseOrderQuery_sync message 40000.Specifically, this figure depicts the arrangement and hierarchy ofvarious components such as one or more levels of packages, entities, anddatatypes, shown here as 40000 through 40010. As described above,packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example,PurchaseOrderTrackingViewERPByPurchaseOrderQuery_sync message 40000includes, among other things, Selection 40006. Accordingly,heterogeneous applications may communicate using this consistent messageconfigured as such.

Additionally, FIG. 41 illustrates one example logical configuration ofPurchaseOrderTrackingViewERPByPurchaseOrderResponse_sync message 41000.Specifically, this figure depicts the arrangement and hierarchy ofvarious components such as one or more levels of packages, entities, anddatatypes, shown here as 41000 through 41054. As described above,packages may be used to represent hierarchy levels. Entities arediscrete business elements that are used during a business transaction.Data types are used to type object entities and interfaces with astructure. For example,PurchaseOrderTrackingViewERPByPurchaseOrderResponse message 41000includes, among other things, PurchaseOrderTrackingView 41006.Accordingly, heterogeneous applications may communicate using thisconsistent message configured as such.

FIGS. 42-1 through 42-16 show an OrderTrackingViewMessage 42000 package.The OrderTrackingViewMessage 42000 package includes anOrderTrackingViewMessage 42002 entity. The OrderTrackingViewMessage42002 entity is a <MessageDataType> 42004 data type. TheOrderTrackingViewMessage 42000 package includes various packages, namelya MessageHeader 42006 package, an OrderTrackingView 42012 package and aLog 42316 package.

The MessageHeader 42006 package includes a MessageHeader 42008 entity.The MessageHeader 42008 entity is a BusinessDocumentMessageHeader 42010data type. The BusinessDocumentMessageHeader can include businessinformation from the perspective of the sender application for theidentifying and processing of a business document (instance) within a(technical) message (if applicable, with a reference to a previousinstallation).

The OrderTrackingView 42012 package includes an OrderTrackingView 42014entity. The OrderTrackingView 42014 entity is an <MT>OrdTrckgVw 42016data type. The OrderTrackingView 42012 package includes an Item 42026package. The OrderTrackingView 42014 entity includes various attributes,namely an ID 42018 attribute and a TypeCode 42022 attribute. The ID42018 attribute is a BusinessTransactionDocumentID 42020 data type. TheBusinessTransactionDocumentID is a unique identifier for a businesstransaction document.

The TypeCode 42022 attribute is a BusinessTransactionDocumentTypeCode42024 data type. The BusinessTransactionDocumentTypeCode is a codedrepresentation of a document type that occurs in business transactions.The document type describes the (business) nature of similar documentsand defines basic features of this type of document.

The Item 42026 package includes an Item 42028 entity. The Item 42028entity is a <MT>Itm 42030 data type. The Item 42026 package includesvarious packages, namely a Product 42036 package, a Quantity 42122package, a Party 42140 package, a Date 42162 package, a Status 42184package, a PredecessorBTDReference 42212 package, a LogisticPackage42222 package and a ScheduleLine 42256 package.

The Item 42028 entity includes a BusinessTransactionDocumentReference42032 attribute. The BusinessTransactionDocumentReference 42032attribute is a BusinessTransactionDocumentReference 42034 data type. TheBusinessTransactionDocumentReference is a unique reference to otherbusiness documents or business document items that are of significancewithin each respective business process. Furthermore, a reference to anitem within the same business document can be supported. In someimplementations, a leading BusinessTransactionDocumentID may also beentered and therefore double maintained.

The Product 42036 package includes various entities, namely a Product42038 entity, a ProductDescription 42106 entity and a Name . . . 42112entity. The Product 42038 entity is a <MT>ItmProd 42040 data type. TheItmProd is an identification, description and classification of aproduct within a business transaction document item. The Product 42038entity includes a Product 42042 subordinate entity. Product informationcan be entered from a perspective of a referenced business transactiondocument. For example, a ProductInternalID of a PurchaseOrder may be,for a derived SalesOrder, a ProductBuyerID.

The BusinessTransactionDocumentProduct includes information that isexchanged in business documents about a product and in accordance withcommon business understanding. This information identifies the productand product type, and describes the product. In some implementations, atleast one product identifying element is filled. The Product 42042entity includes various attributes, namely an InternalID 42046attribute, a StandardID 42050 attribute, a BuyerID 42054 attribute, aSellerID 42058 attribute, a ProductRecipientID 42062 attribute, aVendorID 42066 attribute, a ManufacturerID 42070 attribute, a BillToID42074 attribute, a BillFromID 42078 attribute, a BidderID 42082attribute, a TypeCode 42086 attribute, a Note 42090 attribute, aChangeID 42094 attribute, a DiscontinuationIndicator 42098 attribute anda PackageQuantity 42102 attribute.

The InternalID 42046 attribute is a ProductInternalID 42048 data type.The StandardID 42050 attribute is a ProductStandardID 42052 data type.The BuyerID 42054 attribute is a ProductPartyID 42056 data type. TheSellerID 42058 attribute is a ProductPartyID 42060 data type. TheProductRecipientID 42062 attribute is a ProductPartyID 42064 data type.The VendorID 42066 attribute is a ProductPartyID 42068 data type. TheManufacturerID 42070 attribute is a ProductPartyID 42072 data type.

The BillToID 42074 attribute is a ProductPartyID 42076 data type. TheBillFromID 42078 attribute is a ProductPartyID 42080 data type. TheBidderID 42082 attribute is a ProductPartyID 42084 data type. TheTypeCode 42086 attribute is a ProductTypeCode 42088 data type. The Note42090 attribute is a Note 42092 data type. The ChangeID 42094 attributeis a ProductChangeID 42096 data type. The DiscontinuationIndicator 42098attribute is an Indicator 42100 data type. The PackageQuantity 42102attribute is a Quantity 42104 data type.

The ProductDescription entity 42106 includes a BatchID 42108 attribute.The BatchID 42108 can be used whenever a process in an applicationsupports batches as qualifying characteristics of a material. Forexample, a batch can be offered in corresponding service operations. TheBatchID 42108 is a BatchID 42110 data type. The Name . . . 42112 entityincludes an InventoryValuationTypeCode 42114 attribute. TheInventoryValuationTypeCode 42114 attribute uniquely identifiesseparately valuated stocks of a material. The InventoryValuationTypeCode42114 attribute is an InventoryValuationTypeCode 42116 data type. TheName . . . 42112 entity includes a SerialID 42118 attribute. TheSerialID 42118 attribute is a SerialID 42120 data type. The SerialID canbe used whenever a process in an application supports a serial number asa qualifying characteristic of a material. For example, a serial numbermay be offered in corresponding service operations.

The Quantity 42122 package includes a Quantity 42124 entity. TheQuantity 42124 entity is a <MT>ItmQty 42126 data type. The ItmQty is aquantity for a business transaction document item. In someimplementations, quantities referenced from business transactiondocument items are given as quantities with units and their specifictype and/or role code. Type and role code are dependent on the businesstransaction document item type code. The Quantity 42124 entity includesvarious attributes, namely a Quantity 42128 attribute, aQuantityRoleCode 42132 attribute and a QuantityRoleName 42136 attribute.

The Quantity 42128 attribute is a Quantity 42130 data type. The Quantityis a non-monetary numerical specification of an amount in a unit ofmeasurement for a business transaction document item. TheQuantityRoleCode 42132 attribute is a QuantityRoleCode 42134 data type.The QuantityRoleCode is a coded representation of a role of a quantity.The QuantityRoleName 42136 attribute is a Medium Name 42138 data type.The QuantityRoleCode is a name to define a QuantityRole.

The Party 42140 package includes a Party 42142 entity. The Party 42142entity is a <MT>ItmPty 42144 data type. The ItmPty is a Party forbusiness transaction document items. The Party 42142 entity includesvarious attributes, namely a PartyID 42146 attribute, aPartyRoleCategoryCode 42150 attribute, a PartyName 42154 attribute and aPartyRoleCategoryName 42158 attribute.

The PartyID 42146 attribute is a PartyID 42148 data type. The PartyID isa unique identifier for a party. The PartyRoleCategoryCode 42150attribute is a PartyRoleCategoryCode 42152 data type. ThePartyRoleCategoryCode is a coded representation of a PartyRoleCategory.A PartyRoleCategory is a grouping of PartyRoles according toprocess-controlling criteria. A PartyRole with the same name may existfor each PartyRoleCategory.

The PartyName 42154 attribute is a LANGUAGEINDEPENDENT_LONG_Name 42156data type. The PartyName 42154 attribute is a name used to define thePartyID. The PartyRoleCategoryName 42158 attribute is a Medium_Name42160 data type. The PartyRoleCategoryName 42158 attribute is a nameused to define the PartyRoleCategory.

The Date 42162 package includes a Date 42164 entity. The Date 42164entity is a <MT>ItmDte 42166 data type. The Date 42162 is a date forbusiness transaction document items. The Date 42164 entity includes aTimePoint 42168 subordinate entity. The TimePoint 42168 entity includesvarious attributes, namely a TimePoint 42172 attribute, aTimePointRoleCode 42176 attribute and a TimePointRoleName 42180attribute. In some implementations, at least one of the TimePoint or theother listed Period fields is filled. In some implementations, for allbusiness transaction document related TimePoints, the generic TimePointfield and possibly the corresponding TimePointRoleCode are given. Insome implementations, TimePoints are entered in a generic way.

The TimePoint 42172 attribute is a TimePoint 42174 data type. TheTimePoint is a unique time point in a specific time context. The timepoint defines by means of a time and date value, as well as a time zone.The TimePointRoleCode 42176 attribute is a TimePointRoleCode 42178 datatype. The TimePointRoleCode is a coded representation of the role of atime. The TimePointRoleName 42180 attribute is a Medium_Name 42182 datatype. The TimePointRoleName 42180 attribute is a name used to definetheTimePointRoleCode.

The Status 42184 package includes various entities, namely a Status42186 entity. The Status 42186 entity is a <MT>ItmSts 42188 data type.The ItmSts is information about the lifecycle of a business transactiondocument item.

The Status 42186 entity includes various attributes, namely anApprovalStatusCode 42190 attribute, a BlockingStatusCode 42194attribute, a CancellationStatusCode 42200 attribute, a ClosureStatusCode42204 attribute and a ConsistencyStatusCode 42208 attribute. In someimplementations, at least one Status field is filled. Status fields maydepend on the BusinessTransactionDocumentItemTypeCode. In someimplementations, restrictions are given individually.

The ApprovalStatusCode 42190 attribute is an ApprovalStatusCode 42192data type. The ApprovalStatusCode 42190 attribute is a codedrepresentation of an approval status. In some implementations, theApprovalStatusCode 42190 attribute may be maintained in a PurchaseOrder.

The BlockingStatusCode 42194 attribute is a BlockingStatusCode 42196data type. The BlockingStatusCode 42194 attribute is a codedrepresentation of a blocking status of a storage location. In someimplementations, the BlockingStatusCode 42194 attribute may bemaintained in a PurchaseOrder.

The CancellationStatusCode 42200 attribute is a coded representation ofa status of a cancellation. The CancellationStatusCode 42200 attributeis a CancellationStatusCode 42202 data type. In some implementations,the CancellationStatusCode 42200 attribute may be maintained in aPurchaseOrder.

The ClosureStatusCode 42204 attribute is a ClosureStatusCode 42206 datatype. The ClosureStatusCode 42204 attribute is a coded representation ofa closure status. In some implementations, the ClosureStatusCode 422044attribute may be maintained in a PurchaseOrder.

The ConsistencyStatusCode 42208 attribute is anINCONSISTENTCONSISTENT_ConsistencyStatusCode 42210 data type. TheConsistencyStatusCode 42208 attribute is a coded representation of aconsistency status of an object. In some implementations, theConsistencyStatusCode 42208 attribute may be maintained in aPurchaseOrder.

The PredecessorBTDReference 42212 package includes aPredecessorBTDReference 42214 entity. The PredecessorBTDReference 42214entity is a <MT>ItmPredBTDRef 42216 data type. In some implementations,for ERP (Enterprise Resource Planning), a 0 to 1 cardinality is used. Insome implementations, a business transaction document may have onedirect predecessor.

The PredecessorBTDReference 42214 entity includes aBusinessTransactionDocumentReference 42218 attribute. TheBusinessTransactionDocumentReference 42218 attribute is aBusinessTransactionDocumentReference 42220 data type. TheBusinessTransactionDocumentReference 42218 attribute is a uniquereference to other business documents or business document items thatare of significance within each respective business process.Furthermore, a reference to an item within the same business document ispossible.

The LogisticPackage 42222 package includes a LogisticPackage 42224entity. The LogisticPackage 42224 entity is a <MT>ItmLogPackgg 42226data type. In some implementations, a cardinality of 0 to 1 may be usedfor ERP. In some implementations, a business transaction document itemcan be assigned to one LogisticPackage. Further, items of one specificbusiness transaction document may be assigned to the same, identicalTrackedProcessTrackingMainID.

The LogisticPackage 42224 entity includes various attributes, namely aLogisticUnitID 42228 attribute, a HandlingUnitID 42232 attribute, aTypeCode 42236 attribute and a TypeName 42240 attribute. TheLogisticPackage 42224 entity includes a TrackedProcess 42244 subordinateentity.

The LogisticUnitID 42228 attribute is a LogisticUnitID 42230 data type.The LogisticUnitID 42228 attribute is an identification of a logisticunit. The LogisticUnitID can be empty for identified Logistic Units. Insome implementations, the cardinality is 0 to 1.

The HandlingUnitID 42232 attribute is a HandlingUnitID 42234 data type.The HandlingUnitID is a unique identifier for a logistic unit. In someimplementations, the cardinality is 0 to 1.

The TypeCode 42236 attribute is a LogisticPackageTypeCode 42238 datatype. The TypeCode 42236 attribute is a coded representation of a typeof a packing unit as it is used in logistics for storing and shippinggoods. The TypeName 42240 attribute is a Medium_Name 42242 data type.The TypeName 42240 attribute is a name used to define aLogisticPackageType.

The TrackedProcess 42244 entity includes various attributes, namely aTrackingMainID 42248 attribute and a TrackingApplicationObjectURI 42252attribute. The TrackingMainID 42248 attribute is aTrackedProcessTrackingMainID 42250 data type. TheTrackedProcessTrackingMainID identifies the main part of an object whichis tracked by a tracked process and under which the tracked process isalso known. The TrackingApplicationObjectURI 42252 attribute is a URI(Uniform Resource Identifier) 42254 data type. The URI identifies anobject which is represented by this tracking id.

The ScheduleLine 42256 package includes a ScheduleLine 42258 entity. TheScheduleLine 42258 entity is a <MT>ItmSchedLine 42260 data type. In someimplementations, ScheduleLine is used for business transaction documentswith further divisions of their items. If ScheduleLines are available,Quantity and Date nodes of the ScheduleLine can be filled accordingly.

The ScheduleLine 42256 package includes various packages, namely aQuantity 42270 package and a Date 42288 package. The ScheduleLine 42258entity includes various attributes, namely an ID 42262 attribute and aTypeCode 42266 attribute.

The ID 42262 attribute is aBusinessTransactionDocumentItemScheduleLineID 42264 data type. The ID42262 attribute is a unique identifier that uses a deadline to identifya schedule line of a document item within a business transaction. TheTypeCode 42266 attribute is aBusinessTransactionDocumentItemScheduleLineTypeCode 42268 data type. TheBusinessTransactionDocumentItemScheduleLineTypeCode is a codedrepresentation of a type of an ItemScheduleLine, such asRequestedScheduleLine.

The Quantity 42270 package includes a Quantity 42272 entity. TheQuantity 42272 entity is a <MT>ItmSchedLineQty 42274 data type. In someimplementations, quantities referenced from business transactiondocument items are given as quantities with units and their specifictype and/or role code. Type and role code can be dependent on thebusiness transaction document item type code.

The Quantity 42272 entity includes various attributes, namely a Quantity42276 attribute, a QuantityRoleCode 42280 attribute and aQuantityRoleName 42284 attribute. The Quantity 42276 attribute is aQuantity 42278 data type. The Quantity is a non-monetary numericalspecification of an amount in a unit of measurement for a businesstransaction document schedule line item.

The QuantityRoleCode 42280 attribute is a QuantityRoleCode 42282 datatype. The QuantityRoleCode is a coded representation of a role of aquantity. The QuantityRoleName 42284 attribute is a Medium_Name 42286data type. The QuantityRoleCode is a name used to define a QuantityRole.

The Date 42288 package includes various entities, namely a Date 42290entity and a TimePointPeriod 42310 entity. The Date 42290 entity is a<MT>ItmSchedLineDte 42292 data type. In some implementations, at leastone of the TimePoint or the other listed Period fields are filled. Insome implementations, for business transaction document relatedTimePoints, the generic TimePoint field and possibly a correspondingTimePointRoleCode are given.

The Date 42290 entity includes a TimePoint 42294 subordinate entity. TheTimePoint 42294 entity is a <MT>ItmSchedLineTmePt 42296 data type. TheTimePoint 42294 entity includes various attributes, namely a TimePoint42298 attribute, a TimePointRoleCode 42302 attribute and aTimePointRoleName 42306 attribute.

The TimePoint 42298 attribute is a TimePoint 42300 data type. TheTimePoint is a unique time point in a specific time context. The timepoint can be defined by means of a time and date value, as well as atime zone. In some implementations, TimePoints are entered in a genericway.

The TimePointRoleCode 42302 attribute is a TimePointRoleCode 42304 datatype. The TimePointRoleCode is a coded representation of a role of atime. The TimePointRoleName 42306 attribute is a Medium_Name 42308 datatype. The TimePointRoleName 42306 attribute is a name used to define theTimePointRoleCode. The UPPEROPEN_LOCALNORMALISED_DateTimePeriod is adelivery date for confirmed products, or a time period in which aservice was rendered. The Log 42316 package includes a Log 42318 entity.The Log 42318 entity is a Log 42320 data type.

FIGS. 43-1 through 43-2 illustrate one example logical configuration ofa PurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync 43000element structure. Specifically, these figures depict the arrangementand hierarchy of various components such as one or more levels ofpackages, entities, and datatypes, shown here as 43000 through Period43038. As described above, packages may be used to represent hierarchylevels. Entities are discrete business elements that are used during abusiness transaction. Data types are used to type object entities andinterfaces with a structure. For example, thePurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync 43000includes, among other things, aPurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync 43002.Accordingly, heterogeneous applications may communicate using thisconsistent message configured as such. The data types of the variouspackages, entities, and attributes shown in FIG. 43 are described withrespect to FIG. 42.

The PurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync 43000element structure includes aPurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync 43002entity. The PurchaseOrderTrackingViewERPByPurchaseOrderQueryMessage_sync43000 element structure includes various packages, namely aMessageHeader 43004 and a Selection 43010.

The MessageHeader 43004 package includes a MessageHeader 43006 entity.The MessageHeader 43006 entity has a cardinality of 1 43008 meaning thatfor each instance of the MessageHeader 43004 package there is oneMessageHeader 43006 entity. The Selection 43010 package includes aPurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity. ThePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity has acardinality of 1 43014 meaning that for each instance of the Selection43010 package there is onePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity. ThePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity includesvarious attributes, namely a PurchaseOrderTrackingViewID 43016, aPurchaseOrderTrackingViewItemID 43020, aPurchaseOrderTrackingViewItemProductInternalID 43024, aPurchaseOrderTrackingViewitemProductSellerID 43028, aPurchaseOrderTrackingViewItemScheduleLineQuantity 43032 and aPurchaseOrderTrackingViewItemScheduleLineDateDeliveryPeriod 43036.

The PurchaseOrderTrackingViewID 43016 attribute has a cardinality of 143018 meaning that for each instance of thePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity there isone PurchaseOrderTrackingViewID 43016 attribute. ThePurchaseOrderTrackingViewItemID 43020 attribute has a cardinality of 0 .. . 1 43022 meaning that for each instance of thePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity there maybe one PurchaseOrderTrackingViewItemID 43020 attribute. ThePurchaseOrderTrackingViewItemProductInternalID 43024 attribute has acardinality of 0 . . . 1 43026 meaning that for each instance of thePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity there maybe one PurchaseOrderTrackingViewItemProductInternalID 43024 attribute.The PurchaseOrderTrackingViewItemProductSellerID 43028 attribute has acardinality of 0 . . . 1 43030 meaning that for each instance of thePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity there maybe one PurchaseOrderTrackingViewItemProductSellerID 43028 attribute. ThePurchaseOrderTrackingViewItemScheduleLineQuantity 43032 attribute has acardinality of 0 . . . 1 43034 meaning that for each instance of thePurchaseOrderTrackingViewSelectionByPurchaseOrder 43012 entity there maybe one PurchaseOrderTrackingViewItemScheduleLineQuantity 43032attribute. ThePurchaseOrderTrackingViewItemScheduleLineDateDeliveryPeriod 43036attribute has a cardinality of 0 . . . 1 43038 meaning that for eachinstance of the PurchaseOrderTrackingViewSelectionByPurchaseOrder 43012entity there may be onePurchaseOrderTrackingViewItemScheduleLineDateDeliveryPeriod 43036attribute.

FIGS. 44-1 through 44-12 illustrate one example logical configuration ofa PurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync 44000element structure. Specifically, these figures depict the arrangementand hierarchy of various components such as one or more levels ofpackages, entities, and datatypes, shown here as 44000 through Logcardinality 44276. As described above, packages may be used to representhierarchy levels. Entities are discrete business elements that are usedduring a business transaction. Data types are used to type objectentities and interfaces with a structure. For example, thePurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync 44000includes, among other things, aPurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync 44002.Accordingly, heterogeneous applications may communicate using thisconsistent message configured as such. The data types of the variouspackages, entities, and attributes shown in FIG. 44 are described withrespect to FIG. 42.

The PurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync44000 element structure includes aPurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync 44002entity. ThePurchaseOrderTrackingViewERPByPurchaseOrderResponseMessage_sync 44000element structure includes various packages, namely a MessageHeader44004, a PurchaseOrderTrackingView 44010 and a Log 44272.

The MessageHeader 44004 package includes a MessageHeader 44006 entity.The MessageHeader 44006 entity has a cardinality of 1 44008 meaning thatfor each instance of the MessageHeader 44004 package there is oneMessageHeader 44006 entity. The PurchaseOrderTrackingView 44010 packageincludes a PurchaseOrderTrackingView 44012 entity. ThePurchaseOrderTrackingView 44010 package includes an Item 44024 package.

The PurchaseOrderTrackingView 44012 entity has a cardinality of 1 44014meaning that for each instance of the PurchaseOrderTrackingView 44010package there is one PurchaseOrderTrackingView 44012 entity. ThePurchaseOrderTrackingView 44012 entity includes various attributes,namely an ID 44016 and a TypeCode 44020. The ID 44016 attribute has acardinality of 1 44018 meaning that for each instance of thePurchaseOrderTrackingView 44012 entity there is one ID 44016 attribute.The TypeCode 44020 attribute has a cardinality of 1 44022 meaning thatfor each instance of the PurchaseOrderTrackingView 44012 entity there isone TypeCode 44020 attribute.

The Item 44024 package includes various entities, namely an Item 44026and an URI 44208. The Item 44024 package includes various packages,namely a Product 44034, a Quantity 44116, a Party 44134, a Date 44158, aPredecessorBTDReference 44180, a LogisticPackage 44190 and aScheduleLine 44214. The Item 44026 entity has a cardinality of 0 . . . N44028 meaning that for each instance of the Item 44024 package there maybe one or more Item 44026 entities. The Item 44026 entity includes aBusinessTransactionDocumentReference 44030 attribute. TheBusinessTransactionDocumentReference 44030 attribute has a cardinalityof 1 44032 meaning that for each instance of the Item 44026 entity thereis one BusinessTransactionDocumentReference 44030 attribute.

The URI 44208 entity has a cardinality of 0 . . . 1 44212 meaning thatfor each instance of the Item 44024 package there may be one URI 44208entity. The Product 44034 package includes a Product 44036 entity. TheProduct 44036 entity has a cardinality of 0 . . . 1 44038 meaning thatfor each instance of the Product 44034 package there may be one Product44036 entity. The Product 44036 entity includes various attributes,namely a BatchID 44104, an InventoryValuationTypeCode 44108 and aSerialID 44112. The Product 44036 entity includes a Product 44040subordinate entity. The BatchID 44104 attribute has a cardinality of 0 .. . 1 44106 meaning that for each instance of the Product 44036 entitythere may be one BatchID 44104 attribute. The InventoryValuationTypeCode44108 attribute has a cardinality of 0 . . . 1 44110 meaning that foreach instance of the Product 44036 entity there may be oneInventoryValuationTypeCode 44108 attribute. The SerialID 44112 attributehas a cardinality of 0 . . . 1 44114 meaning that for each instance ofthe Product 44036 entity there may be one SerialID 44112 attribute.

The Product 44040 entity has a cardinality of 1 44042 meaning that foreach instance of the Product 44036 entity there is one Product 44040entity. The Product 44040 entity includes various attributes, namely anInternalID 44044, a StandardID 44048, a BuyerID 44052, a SellerID 44056,a ProductRecipientID 44060, a VendorID 44064, a ManufacturerID 44068, aBillToID 44072, a BillFromID 44076, a BidderID 44080, a TypeCode 44084,a Note 44088, a ChangeID 44092, a DiscontinuationIndicator 44096 and aPackageQuantity 44100.

The InternalID 44044 attribute has a cardinality of 0 . . . 1 44046meaning that for each instance of the Product 44040 entity there may beone InternalID 44044 attribute. The StandardID 44048 attribute has acardinality of 0 . . . 1 44050 meaning that for each instance of theProduct 44040 entity there may be one StandardID 44048 attribute. TheBuyerID 44052 attribute has a cardinality of 0 . . . 1 44054 meaningthat for each instance of the Product 44040 entity there may be oneBuyerID 44052 attribute. The SellerID 44056 attribute has a cardinalityof 0 . . . 1 44058 meaning that for each instance of the Product 44040entity there may be one SellerID 44056 attribute. The ProductRecipientID44060 attribute has a cardinality of 0 . . . 1 44062 meaning that foreach instance of the Product 44040 entity there may be oneProductRecipientID 44060 attribute. The VendorID 44064 attribute has acardinality of 0 . . . 1 44066 meaning that for each instance of theProduct 44040 entity there may be one VendorID 44064 attribute. TheManufacturerID 44068 attribute has a cardinality of 0 . . . 1 44070meaning that for each instance of the Product 44040 entity there may beone ManufacturerID 44068 attribute.

The BillToID 44072 attribute has a cardinality of 0 . . . 1 44074meaning that for each instance of the Product 44040 entity there may beone BillToID 44072 attribute. The BillFromID 44076 attribute has acardinality of 0 . . . 1 44078 meaning that for each instance of theProduct 44040 entity there may be one BillFromID 44076 attribute. TheBidderID 44080 attribute has a cardinality of 0 . . . 1 44082 meaningthat for each instance of the Product 44040 entity there may be oneBidderID 44080 attribute. The TypeCode 44084 attribute has a cardinalityof 0 . . . 1 44086 meaning that for each instance of the Product 44040entity there may be one TypeCode 44084 attribute. The Note 44088attribute has a cardinality of 0 . . . 144090 meaning that for eachinstance of the Product 44040 entity there may be one Note 44088attribute. The ChangeID 44092 attribute has a cardinality of 0 . . . 144094 meaning that for each instance of the Product 44040 entity theremay be one ChangeID 44092 attribute. The DiscontinuationIndicator 44096attribute has a cardinality of 0 . . . 1 44098 meaning that for eachinstance of the Product 44040 entity there may be oneDiscontinuationIndicator 44096 attribute. The PackageQuantity 44100attribute has a cardinality of 0 . . . 1 44102 meaning that for eachinstance of the Product 44040 entity there may be one PackageQuantity44100 attribute.

The Quantity 44116 package includes a Quantity 44118 entity. TheQuantity 44118 entity has a cardinality of 0 . . . N 44120 meaning thatfor each instance of the Quantity 44116 package there may be one or moreQuantity 44118 entities. The Quantity 44118 entity includes variousattributes, namely a Quantity 44122, a QuantityRoleCode 44126 and aQuantityRoleName 44130. The Quantity 44122 attribute has a cardinalityof 1 44124 meaning that for each instance of the Quantity 44118 entitythere is one Quantity 44122 attribute. The QuantityRoleCode 44126attribute has a cardinality of 1 44128 meaning that for each instance ofthe Quantity 44118 entity there is one QuantityRoleCode 44126 attribute.The QuantityRoleName 44130 attribute has a cardinality of 0 . . . 144132 meaning that for each instance of the Quantity 44118 entity theremay be one QuantityRoleName 44130 attribute.

The Party 44134 package includes a Party 44136 entity. The Party 44136entity has a cardinality of 0 . . . N 44138 meaning that for eachinstance of the Party 44134 package there may be one or more Party 44136entities. The Party 44136 entity includes various attributes, namely aPartyID 44140, a PartyRoleCategoryCode 44146, a PartyName 44150 and aPartyRoleCategoryName 44154. The PartyID 44140 attribute has acardinality of 1 44144 meaning that for each instance of the Party 44136entity there is one PartyID 44140 attribute. The PartyRoleCategoryCode44146 attribute has a cardinality of 1 44148 meaning that for eachinstance of the Party 44136 entity there is one PartyRoleCategoryCode44146 attribute. The PartyName 44150 attribute has a cardinality of 0 .. . 1 44152 meaning that for each instance of the Party 44136 entitythere may be one PartyName 44150 attribute. The PartyRoleCategoryName44154 attribute has a cardinality of 0 . . . 1 44156 meaning that foreach instance of the Party 44136 entity there may be onePartyRoleCategoryName 44154 attribute.

The Date 44158 package includes a Date 44160 entity. The Date 44160entity has a cardinality of 0 . . . 1 44162 meaning that for eachinstance of the Date 44158 package there may be one Date 44160 entity.The Date 44160 entity includes a TimePoint 44164 subordinate entity. TheTimePoint 44164 entity has a cardinality of 0 . . . N 44166 meaning thatfor each instance of the Date 44160 entity there may be one or moreTimePoint 44164 entities. The TimePoint 44164 entity includes variousattributes, namely a TimePoint 44168, a TimePointRoleCode 44172 and aTimePointRoleName 44176. The TimePoint 44168 attribute has a cardinalityof 1 44170 meaning that for each instance of the TimePoint 44164 entitythere is one TimePoint 44168 attribute. The TimePointRoleCode 44172attribute has a cardinality of 1 44174 meaning that for each instance ofthe TimePoint 44164 entity there is one TimePointRoleCode 44172attribute. The TimePointRoleName 44176 attribute has a cardinality of 0. . . 1 44178 meaning that for each instance of the TimePoint 44164entity there may be one TimePointRoleName 44176 attribute.

The PredecessorBTDReference 44180 package includes aPredecessorBTDReference 44182 entity. The PredecessorBTDReference 44182entity has a cardinality of 0 . . . N 44184 meaning that for eachinstance of the PredecessorBTDReference 44180 package there may be oneor more PredecessorBTDReference 44182 entities. ThePredecessorBTDReference 44182 entity includes aBusinessTransactionDocumentReference 44186 attribute. TheBusinessTransactionDocumentReference 44186 attribute has a cardinalityof 1 44188 meaning that for each instance of the PredecessorBTDReference44182 entity there is one BusinessTransactionDocumentReference 44186attribute.

The LogisticPackage 44190 package includes a LogisticPackage 44192entity. The LogisticPackage 44192 entity has a cardinality of 0 . . . N44194 meaning that for each instance of the LogisticPackage 44190package there may be one or more LogisticPackage 44192 entities. TheLogisticPackage 44192 entity includes a HandlingUnitID 44196 attribute.The LogisticPackage 44192 entity includes a TrackedProcess 44200subordinate entity. The HandlingUnitID 44196 attribute has a cardinalityof 0 . . . 1 44198 meaning that for each instance of the LogisticPackage44192 entity there may be one HandlingUnitID 44196 attribute.

The TrackedProcess 44200 entity has a cardinality of 0 . . . 1 44202meaning that for each instance of the LogisticPackage 44192 entity theremay be one TrackedProcess 44200 entity. The TrackedProcess 44200 entityincludes various attributes, namely a TrackingMainID 44204 and aTrackingApplicationObjectURL 44210. The TrackingMainID 44204 attributehas a cardinality of 1 44206 meaning that for each instance of theTrackedProcess 44200 entity there is one TrackingMainID 44204 attribute.The TrackingApplicationObjectURL 44210 attribute has a cardinality of 0. . . 1 44212 meaning that for each instance of the TrackedProcess 44200entity there may be one TrackingApplicationObjectURL 44210 attribute.

The ScheduleLine 44214 package includes a ScheduleLine 44216 entity. TheScheduleLine 44214 package includes various packages, namely a Quantity44228 and a Date 44246. The ScheduleLine 44216 entity has a cardinalityof 0 . . . N 44218 meaning that for each instance of the ScheduleLine44214 package there may be one or more ScheduleLine 44216 entities. TheScheduleLine 44216 entity includes various attributes, namely an ID44220 and a TypeCode 44224. The ID 44220 attribute has a cardinality of1 44222 meaning that for each instance of the ScheduleLine 44216 entitythere is one ID 44220 attribute. The TypeCode 44224 attribute has acardinality of 1 44226 meaning that for each instance of theScheduleLine 44216 entity there is one TypeCode 44224 attribute.

The Quantity 44228 package includes a Quantity 44230 entity. TheQuantity 44230 entity has a cardinality of 0 . . . N 44232 meaning thatfor each instance of the Quantity 44228 package there may be one or moreQuantity 44230 entities. The Quantity 44230 entity includes variousattributes, namely a Quantity 44234, a QuantityRoleCode 44238 and aQuantityRoleName 44242. The Quantity 44234 attribute has a cardinalityof 1 44236 meaning that for each instance of the Quantity 44230 entitythere is one Quantity 44234 attribute. The QuantityRoleCode 44238attribute has a cardinality of 1 44240 meaning that for each instance ofthe Quantity 44230 entity there is one QuantityRoleCode 44238 attribute.The QuantityRoleName 44242 attribute has a cardinality of 0 . . . 144244 meaning that for each instance of the Quantity 44230 entity theremay be one QuantityRoleName 44242 attribute.

The Date 44246 package includes a Date 44248 entity. The Date 44248entity has a cardinality of 0 . . . 1 44250 meaning that for eachinstance of the Date 44246 package there may be one Date 44248 entity.The Date 44248 entity includes a DeliveryPeriod 44268 attribute. TheDate 44248 entity includes a TimePoint 44252 subordinate entity. TheDeliveryPeriod 44268 attribute has a cardinality of 0 . . . 1 44270meaning that for each instance of the Date 44248 entity there may be oneDeliveryPeriod 44268 attribute.

The TimePoint 44252 entity has a cardinality of 0 . . . N 44254 meaningthat for each instance of the Date 44248 entity there may be one or moreTimePoint 44252 entities. The TimePoint 44252 entity includes variousattributes, namely a TimePoint 44256, a TimePointRoleCode 44260 and aTimePointRoleName 44264. The TimePoint 44256 attribute has a cardinalityof 1 44258 meaning that for each instance of the TimePoint 44252 entitythere is one TimePoint 44256 attribute. The TimePointRoleCode 44260attribute has a cardinality of 1 44262 meaning that for each instance ofthe TimePoint 44252 entity there is one TimePointRoleCode 44260attribute. The TimePointRoleName 44264 attribute has a cardinality of 144266 meaning that for each instance of the TimePoint 44252 entity thereis one TimePointRoleName 44264 attribute.

The Log 44272 package includes a Log 44274 entity. The Log 44274 entityhas a cardinality of 1 44276 meaning that for each instance of the Log44272 package there is one Log 44274 entity.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. Accordingly, otherimplementations are within the scope of the following claims.

What is claimed is:
 1. A computer readable medium including program codefor providing a message-based interface for performing an individualmaterial bill of material service, the interface exposing at least oneservice as defined in a service registry, wherein upon execution theprogram code executes in an environment of computer systems providingmessage-based services and comprises: program code for receiving, from aservice consumer, a first message for processing information for a listthat comprises the elements defining and describing the components toassemble an individual material bill of material; program code forinvoking an individual material bill of material business object,wherein the business object is a logically centralized, semanticallydisjointed object for representing information for a list that comprisesthe elements defining and describing the components to assemble anindividual material bill of material, and comprises data logicallyorganized as: an individual material bill of material root node; and avariant subordinate node and wherein the variant node contains: alocation subordinate node; and an item subordinate node and wherein theitem node contains a change state subordinate node; and program code forinitiating transmission of a message to a heterogeneous secondapplication, executing in the environment of computer systems providingmessage-based services, based on the data in the individual materialbill of material business object, the message comprising an individualmaterial bill of material message entity, a message header package, andan individual material bill of material package.
 2. A computer readablemedium including program code for providing a message-based interfacefor performing an individual material bill of material service, thesoftware comprising computer readable instructions embodied on tangiblemedia, wherein upon execution the software executes in a landscape ofcomputer systems providing message-based services and comprises: programcode for initiating transmission of a message to a heterogeneous secondapplication, executing in the environment of computer systems providingmessage-based services, based on data in an individual material bill ofmaterial business object invoked by the second application, wherein thebusiness object is a logically centralized, semantically disjointedobject for representing information for a list that comprises theelements defining and describing the components to assemble anindividual material bill of material and comprises data logicallyorganized as: an individual material bill of material root node; and avariant subordinate node and wherein the variant node contains: alocation subordinate node; and an item subordinate node and wherein theitem node contains a change state subordinate node; and the messagecomprising an individual material bill of material message entity, amessage header package, and an individual material bill of materialpackage; and program code for receiving a second message from the secondapplication, the second message associated with the invoked individualmaterial bill of material business object and in response to the firstmessage.
 3. A distributed system operating in a landscape of computersystems providing message-based services, the system processing businessobjects involving an individual material bill of material service andcomprising: memory storing a business object repository storing aplurality of business objects; wherein each business object is alogically centralized, semantically disjointed object and at least oneof the business objects is for representing information for a list thatcomprises the elements defining and describing the components toassemble an individual material bill of material and comprises datalogically organized as: an individual material bill of material rootnode; and a variant subordinate node and wherein the variant nodecontains: a location subordinate node; and an item subordinate node andwherein the item node contains a change state subordinate node; and agraphical user interface remote from the memory for presenting dataassociated with an invoked instance of the individual material bill ofmaterial business object, the interface comprising computer readableinstructions embodied on tangible media.
 4. A computer readable mediumincluding program code for providing a message-based interface forperforming an order tracking view service, the interface exposing atleast one service as defined in a service registry, wherein uponexecution the program code executes in an environment of computersystems providing message-based services and comprises: program code forreceiving, from a service consumer, a first message for processinginformation for all document information for the follow-on businesstransactions for tracking and completion of a specified order; programcode for invoking an order tracking view business object, wherein thebusiness object is a logically centralized, semantically disjointedobject for representing information for document information for thefollow-on business transactions for tracking and completion of aspecified order, and comprises data logically organized as: an ordertracking view root node; and an item subordinate node and wherein theitem node contains: a product subordinate node; a quantity subordinatenode; a party subordinate node; a date subordinate node; a predecessorbusiness transaction document reference subordinate node; a logisticpackage subordinate node; and a schedule line subordinate node andwherein the schedule line node contains: a quantity subordinate node;and a date subordinate node; and program code for initiatingtransmission of a message to a heterogeneous second application,executing in the environment of computer systems providing message-basedservices, based on the data in the order tracking view business object,the message comprising a purchase order tracking view enterpriseresource planning by purchase order response message entity, a messageheader package, and a purchase order tracking view package, and a logpackage.
 5. A computer readable medium including program code forproviding a message-based interface for performing an order trackingview service service, the software comprising computer readableinstructions embodied on tangible media, wherein upon execution thesoftware executes in a landscape of computer systems providingmessage-based services and comprises: program code for initiatingtransmission of a message to a heterogeneous second application,executing in the environment of computer systems providing message-basedservices, based on data in a order tracking view business object invokedby the second application, wherein the business object is a logicallycentralized, semantically disjointed object for representing informationfor document information for the follow-on business transactions fortracking and completion of a specified order and comprises datalogically organized as: an order tracking view root node; and an itemsubordinate node and wherein the item node contains: a productsubordinate node; a quantity subordinate node; a party subordinate node;a date subordinate node; a predecessor business transaction documentreference subordinate node; a logistic package subordinate node; and aschedule line subordinate node and wherein the schedule line nodecontains: a quantity subordinate node; and a date subordinate node; andthe message comprising a purchase order tracking view enterpriseresource planning by purchase order response message entity, a messageheader package, and a purchase order tracking view package, and a logpackage; and program code for receiving a second message from the secondapplication, the second message associated with the invoked ordertracking view business object and in response to the first message.
 6. Adistributed system operating in a landscape of computer systemsproviding message-based services, the system processing business objectsinvolving an order tracking view service and comprising: memory storinga business object repository storing a plurality of business objects;wherein each business object is a logically centralized, semanticallydisjointed object and at least one of the business objects is forrepresenting information for document information for the follow-onbusiness transactions for tracking and completion of a specified orderand comprises data logically organized as: an order tracking view rootnode; and an item subordinate node and wherein the item node contains: aproduct subordinate node; a quantity subordinate node; a partysubordinate node; a date subordinate node; a predecessor businesstransaction document reference subordinate node; a logistic packagesubordinate node; and a schedule line subordinate node and wherein theschedule line node contains: a quantity subordinate node; and a datesubordinate node; and a graphical user interface remote from the memoryfor presenting data associated with an invoked instance of the ordertracking view business object, the interface comprising computerreadable instructions embodied on tangible media.
 7. The program code ofclaim 1, wherein processing includes creating, updating and/orretrieving.